search for: ext3_add_entry

Just had this problem on linux 2.5.50. MikaL

...o with a problem i'm running across. A filesystem under load put itself in readonly mode and the following can be found under dmesg.. any suggestions on root cause? hardware wise it's got a pair of PATA drives connected to a 3ware card in RAID10 configuration. EXT3-fs error (device dm-4): ext3_add_entry: bad entry in directory #14370410: rec_len % 4 != 0 - offset=0, inode=1309281588, rec_len=16761, name_len=78 Aborting journal on device dm-4. ext3_abort called. EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device dm-4) i...

...: EXT3-fs error (device lvm(58,1)): ext3_new_block: Allocating block in system zone - block = 20251151 Oct 19 16:04:39 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_new_block: Allocating block in system zone - block = 20251152 Oct 19 16:04:43 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_add_entry: bad entry in directory #10125314: rec_len %% 4 != 0 - offset=0, inode=4288315399, rec_len=65535, name_len=255 Oct 19 16:04:44 noname last message repeated 53 times Oct 19 16:05:04 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_add_entry: bad entry in directory #10125314: rec_len %% 4 != 0...

Hi, I recently upgraded one of my fileservers from 2.4.16 to 2.4.18 plus the ext3-cvs.patch that Andrew Morton pointed me to for addressing and assertion failure. Since then I have been getting lots of errors like: May 21 14:07:03 glass kernel: EXT3-fs error (device md(9,0)): ext3_add_entry: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927, name_len=109 May 21 14:07:23 glass kernel: EXT3-fs error (device md(9,0)): ext3_readdir: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927, name_len=109 May...

...array and built an ext3 file system on it; on trying to copy data off the 200GB RAID it is replacing I'm starting to see errors of the form: kernel: EXT3-fs error (device md(9,2)): ext3_new_block: Allocating block in system zone - block = 140509185 and kernel: EXT3-fs error (device md(9,2)): ext3_add_entry: bad entry in directory #70254593: rec_len %% 4 != 0 - offset=28, inode=23880564, rec_len=21587, name_len=76 and kernel: raid5: multiple 1 requests for sector 281018464 This is on an x86 which has been running fine on the smaller raid for years (albeit Reiser); the array is built from 5 200GB We...

...stantiated. fs/ext3/namei.c | 11 +++++------ 1 files changed, 5 insertions(+), 6 deletions(-) --- 24/fs/ext3/namei.c~ext3-use-after-free Sun Dec 15 11:27:50 2002 +++ 24-akpm/fs/ext3/namei.c Sun Dec 15 11:27:50 2002 @@ -429,8 +429,11 @@ static int ext3_add_nondir(handle_t *han { int err = ext3_add_entry(handle, dentry, inode); if (!err) { - d_instantiate(dentry, inode); - return 0; + err = ext3_mark_inode_dirty(handle, inode); + if (err == 0) { + d_instantiate(dentry, inode); + return 0; + } } ext3_dec_count(handle, inode); iput(inode); @@ -465,7 +468,6 @@ static int ext3_create (...

...t; on trying to copy data off the 200GB RAID it is replacing I'm > starting to see errors of the form: > > kernel: EXT3-fs error (device md(9,2)): ext3_new_block: Allocating block in > system zone - block = 140509185 > > and > > kernel: EXT3-fs error (device md(9,2)): ext3_add_entry: bad entry in > directory #70254593: rec_len %% 4 != 0 - offset=28, inode=23880564, > rec_len=21587, name_len=76 > > and > > kernel: raid5: multiple 1 requests for sector 281018464 I had exactly these symptoms about a year ago in 2.4.18. I found and fixed the problem and have...

...ournal aborted, and then nfsd Oopsed inside ext3. I rebooted and fscked the filesystem and it found nothing interesting - see output below. So I suspect ext3 has a problem somewhere. I'll see if I can break it again :-) NeilBrown Aug 6 15:22:05 adams kernel: EXT3-fs error (device md1): ext3_add_entry: bad entry in directory #41 009295: rec_len is smaller than minimal - offset=0, inode=3265411686, rec_len=0, name_len=0 Aug 6 15:22:05 adams kernel: Aborting journal on device sda4. Aug 6 15:22:05 adams kernel: ext3_abort called. Aug 6 15:22:05 adams kernel: EXT3-fs abort (device md1): ext3_jour...

Dear All Problem with ext3 fs on 3ware 9500S controller: Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #145998372: rec_len is smaller than minim al - offset=0, inode=0, rec_len=0, name_len=0 Dec 7 05:59:50 stams kernel: Aborting journal on device sda1. Dec 7 05:59:50 stams kernel: ext3_abort called. Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_journal_s...

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these