similar to: EXT3 filesystem on scsi device becoming readonly

Hello, I have a problem with directories that contain more than 10000 entries (Ubuntu 8.04.1) or with more than 70000 entries (RHEL 5.2). If you use readdir(3) or readdir64(3) you get one entry twice, with same name and inode. Some analyzing showed that disabling dir_index solves this problem, but I think that this is a bug in the ext3 code, as no other file-system shows this behavior.

Peter, Okay, here are the exact error messages and what leads up to them: -------------------------begin------------------------- Adaptec AHA-2940 Ultra/Ultra w BIOS v.1.23 (c) 1996 adaptec, Inc. all rights Reserved. Press <Ctrl> <A> for SCSI Select (TM) Utility! * SCSI ID: LUN NUMBER #:# 0:0 - IBM-PCCO DGHS - Drive C: (80h) SCSI ID: LUN NUMBER #:# 5:0 - MATSHITA CD_ROM CR-506

Having just spent a day trying to recover a deleted ext3 file for a friend, I'm wondering about this way of maintining undelete information in ext3, like is done for ext2: The last step in the deletion process would be to put back the (previously zeroed) block pointers. Since it gets logged to the journal, I _think_ that this should be safe. The worst that would happen is that, if the plug

An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20060828/ce9c7bc0/attachment.htm>

Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem

Hi - We have an ext3 file system which is 3.5TB in size (on top of lvm). Free are 172049011 out of 854473728 4096K blocks, and 396540654 out of 427245568 inodes. This is using Scientific Linux 4.4 (a RHEL clone). The filesystem consists of multiple backups created with rsync using --link-dest, which hard links files which haven't been modified to the previous copy. There are several hundred

Hello, As a Virtuozzo users we have majority of our diskspace formatted with -i 1024 -b 1024. Lately I discovered that on CentOS 4.6 ext2online barfs when I try to grow such filesystem. Running it with -v -d, it prints lots of lines like: ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b ext2online: 873646830 is a bad size for an ext2 fs! rounding down to 873644033 ... group NNN inode table has

On Tue, Mar 17, 2009 at 02:02:33PM -0700, Randy Dunlap wrote: > Greg KH wrote: > > On Tue, Mar 17, 2009 at 01:26:47PM -0700, Randy Dunlap wrote: > >> Enable all possible OCFS2 kconfig options: > >> > >> > >> > >> In file included from fs/ocfs2/alloc.c:42: > >> fs/ocfs2/journal.h: In function 'ocfs2_begin_ordered_truncate': >

Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the

Hi, I need to understand and to calculate the offset of the beginning of a file within my partition which uses an ext3 filesystem. Can I use dumpe2fs to figure that out, if yes how? Sincerely, William Tambe

Hi list, I'm looking for advice/help in tracking down a problem with a new system I've purchased. I have a beige box server with a Gigabyte GA-M51GM-S2G motherboard. It has the nVidia MCP51 SATA controller with 3 250 gig Western Digital hard drives attached to it. It seems that when doing a considerable amount of file writing, the filesystem will become read-only. See attached dmesg

I tried it on loop. 1. mount /dev/loop0 /mnt/test -t ext3 2. cp files to 100% full 3. umount /mnt/test 4. fsck.ext3 -f /dev/loop0 Inode xxxxx, i_blocks is xxx, should be yyy. Fix?

Greetings from beautiful Alabama. You have requested for people to let you know if they are having any problem: I am a professor in the Department of Mathematics, Auburn University. Among other activities, I do a lot of Linux installations on older computers, many of which are old Gateway Pentium Pro boxes which came with Adaptec 2940 SCSI cards and SCSI CD. I have burned several Slackware 8.1

Hi folks -- My machine is a RHEL 3 with 2.4 kernel installed - with some large ext3 filesystems on drives connected internally ( >200G) Now, When this system crashed (for eg:- a CPU panic /hardware error ) - e2fsck on this filesystem seems to be taking a long time to return thereby adding to the overall downtime of this system. could there be any workarounds for my issue? say for

This option is needed by vdsm for writing the ovf to a specific directory. The default is current directory. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1176598 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/cmdline.ml | 5 +++++ v2v/output_vdsm.ml | 16 +++++++--------- v2v/output_vdsm.mli | 1 + v2v/test-v2v-o-vdsm-options.sh |

I am running into performance issues with ext3. Historically we had our image files (pictures of cars, currently 5.3 million) sub divided into a directory structure [0-9]/[0-9]/[0-9]/[0-9], where we would take the first 4 letters/numbers of the file name and use that to put it into this structure. Letters [a-cA-C] would become a 0, [d-fD-F] a 1, etc. As the file names used to be based on VIN

Hi, I would like to know if there are any plans to introduce a creation timestamp in future ext3/4 versions. Having a 4th timestamp saving the creation time would be very good for projekts like Samba for example. It would be important that creation time can also be set manually later on by some system call. Systems like FreeBSD's UFS and Solais' ZFS already support creation times.

This may or may not be ext3 related but I am trying to find any pointers which might help me. I got a number of HP Proliant DL380 g5 with a P400 controller and also two qla2400 cards. The OS is RedHat EL4 U5 x86_64. Every time during reboot these systems panic after the last umount and I believe before the cciss driver is getting unloaded. The last messages I am able to see are: md: stopping

I was just playing with git 1.5.3.8 and btrfs 0.11, and I noticed something odd. If I prepare a very simple repository: $ mkdir foo $ cd foo $ git init Initialized empty Git repository in .git/ $ echo hi > blort $ git add . $ git commit -m create Created initial commit 4ae9415: create 1 files changed, 1 insertions(+), 0 deletions(-) create mode 100644 blort and then

Hello. I'm having serious issues with ext3; any insight would be greatly appreciated: _____ Overview: I believe ext3 is supposed to be recoverable in the case of a power failure by replaying the log. However, on two separate computers (running different operatings systems too), this has been everything but the case. _____ Specifics: Sometimes, my kernel will hard-freeze and I'll