On Thu, Jul 17, 2008 at 5:08 PM, Theodore Tso <tytso@xxxxxxx> wrote: > Vegard, > > How big is the filesystem? Is there any chance you can make a > compressed e2image of the file? (This will not include file contents, > but does reveal the names of the file.) Given the nature of the bug > which you are reporting, it should be safe to scramble the names of > the filenames using the -s option if that would make you feel more > comfortable. Oh, just 2M. It doesn't contain anything but copies of /bin/bash. I basically just made a crash-tester script that corrupts a dummy filesystem on purpose. But it seems that it might be partly my own fault for not protecting the bits in the filesystem image that say "oh, proceed on error". But I do have a feeling that the filesystem should not be able to say this in the first place. Because those bits can be corrupted legitimately in other ways too! http://folk.uio.no/vegardno/linux/corrupt.tar.bz2 Is there a way to override the "Errors behavior: Continue" information which is present in the filesystem? Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- 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
