Hi, On Tue, Oct 16, 2007 at 08:20:59PM -0500, Eric Sandeen wrote: > Martin Habets wrote: > > Hello, > > > > I ran the ltp-full-20070930 tests on 2.6.23-rc9-mph4 (sparc32 SMP), and am > > seeing the following warnings: > > This makes me a little nervous about my change > ef2b02d3e617cb0400eedf2668f86215e1b0e6af > (ext34: ensure do_split leaves enough free space in both blocks) > > Do you know when this first showed up? Could you test -rc6?
Thanks for the input. Tried this on -rc6, it behaves worse. Besides the earlier warnings EXT3-fs warning (device sdb4): ext3_rename: Deleting old file (268753), 2, error=-2 I also get a lot of these EXT3-fs error (device sdb4): ext3_add_entry: bad entry in directory #268753: rec_len is smaller than minimal - offset=56, inode=8026488, rec_len=0, name_len=0 and these at the end of the test: EXT3-fs warning (device sdb4): ext3_unlink: Deleting nonexistent file (268761), 0 EXT3-fs error (device sdb4): ext3_readdir: bad entry in directory #268753: rec_len is smaller than minimal - offset=56, inode=8026488, rec_len=0, name_len=0 EXT3-fs error (device sdb4): empty_dir: bad entry in directory #268753: rec_len is smaller than minimal - offset=56, inode=8026488, rec_len=0, name_len=0 The FS is still mounted rw. > You say you can reproduce it; have you checked (fsck'd) the filesystem > in between, and is it in good shape? Like you, I rerun rename14 stand-alone at the moment. I didnt do an explicit fschk between all runs, but I also did 2 reboots which did check the FS. I'll try to bisect the original ext3_rename warning further. -- Martin - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
