Ted, one more thing I did not mention up to now: my system is Hardy-amd64.
My personal guess now is that it is not e2fsck itself, but in co- operation with some other part of the system (gvfs, nautilus, hal ?? whatever). And as v1.41.0 of e2fsprogs seems to handle the matter smoothly at least under Lenny, my recommendation for a fix is to just upgrade e2fsprogs and not spending more efforts in solving something which probably has been solved. Many thanks from my side - you did me and many others a big favour by teaching how to read the 'proprietary ext3 from QNAP'. That's more than expected! And as said, I cannot create such a virgin reproducible file system right now as my box is away for repair. If you do not want to propose upgrade of e2fsprogs in Hardy, we will have to wait till I can create an untouched/spoiled filesystem to use for tracing. Many thanks, 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
