If said in my first post, that the file system was created by QNAP TS-209 NAS. It is an ext3 file system, but with some patches from QNAP applied (as far as I know to speed up RAID1).
This filesystem cannot be mounted on standard Linux PC's - but it is definitely ext3! And that's why I have run e2fsck on it - at least tried: on openSUSE with e2fsprogs 1.39 the check (with -n option!) does not run, see post before, but it does not crash! on Hardy with v1.40 e2fsck just crashes - that's why I reported the bug on Lenny with 1.41 e2fsck runs through fine and displays the faulty things, and without the -n option also corrects the errors. So conclusion in the order I have performed: filesystem is corrupted cannot be mounted Hardy: e2fsck crashes OpenSUSE e2fsck reports message and exits Lenny reports the faulty things, is able to correct some, but not all. Filesystem can still not be mounted - but that is another story and no reason to crash e2fsck If you need prove I'll do copy you mtab or whatever you like to show that it is NOT mounted! Ingo -- e2fsck crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/257048 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
