So, forgot to mention: if you want to reproduce the crash, you need a corrupted filesystem like I have it here.
That neiter e2fsck can repair it - its my fault (don't need the data anyhow) But that e2fsck in Hardy crashes instead of displaying a message and exits, is a bug! The filesystem still is corrupt and despite Lenny did fix a lot, it still is nos usable. And, only Hardy's e2fsck still crashes when I call it! -- 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
