Re: ext3 filesystem corruption in user mode linux

[Chris Frey]

On Fri, Sep 24, 2010 at 12:14:10AM -0400, Chris Frey wrote:
> If I do some heavy CPU and disk work in the guest, something like this:
> 
> 	# (cd /usr && tar cjf - portage) | tar xjf -
> 	# rm -rf portage
> 
> Then the filesystem corrupts itself, giving errors like the following
> in dmesg, during the rm:
> 
>     EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 51715


Update:

So far I have been unable to make 2.6.32.21 corrupt its filesystem
when running as the UML kernel (Host 2.6.35.4, UML 2.6.32.21)

When running UML 2.6.33.7, I get similar errors:

EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 21397
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13257
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13257
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 21403
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 21403
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13262
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13262
EXT3-fs error (device ubda): htree_dirblock_to_tree: bad entry in directory #13269: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT3-fs (ubda): warning: empty_dir: bad directory (dir #13269) - no `.' or `..'
EXT3-fs (ubda): warning: ext3_rmdir: empty directory has nlink!=2 (3)


If anyone wants me to test a specific UML kernel, please let me know.

- Chris

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/