Many thanks Ted, I think you hit the point! For sure lenny did not 'repair' the file system, but left it in an unusable condition. I was able to even recover some of the filesystem (root directories9 by using 'debugfs' 'open /dev/sdc3' ...
So I now know where to go and I discard the unusable partitition. But I will get my NAS back and repaired soon (I hope) and then be able to create a 'virgin QNAP ext3' and check with Lenny or even Intrepid whether it is a ext4-alpha! So for the moment, dont't worry about the ext4 story, just fsck.ext3 should not crash when operating on such a 'homebrew ext4'. I do attach/upload the Outputs from Lenny for the 2 runs of e2fsck here as 'QNAP-fsck.txt' Many thanks, Ingo P.S.: when my NAS is back, I probably can create such a beast of filesystem for testing ;-) ** Attachment added: "Leny's output of e2fsck" http://launchpadlibrarian.net/16762669/QNAP-fsck.txt -- 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
