On Wed, 2010-05-12 at 17:00 +0200, Jan Kara wrote: > Could you get the filesystem image with: e2image -r /dev/sdb2 buggy-image > bzip2 it and make it available somewhere? Maybe I could guess something > from the way the filesystem gets corrupted. > Oh, and also overwrite the partition with zeros before calling mkfs to make > the analysis simpler. Here we go. Created a smaller partition (100MB). dd'ed /dev/zero to it, dd'ed it off to NFS host to locally cmp it with /dev/zero to make sure it's nice and clean. It is. Then mkfs.ext3, mount, rsync over /usr/lib of my test root, unmount, and dd it off to the NFS host again. The result shows the same errors with fsck.ext3 -n -f ./test.img I uploaded it at: http://gate.crashing.org/~benh/test.img.bz2 Cheers, Ben. > > In fact, if I do ls /mnt/test/usr/bin/ I see debconf but if I do > > ls /mnt/test/usr/bin/chrt then I get No such file or directory. > > > > So something is badly wrong :-) > > > > Now, trying without the dir_index feature (mkfs.ext3 -O ^dir_index) > > and it works fine. All my md5sum's are correct and fsck passes. > Funny. Not sure how that could happen... > > Honza -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
