You do realize that e2image doesn't contain any data blocks --- just file system metadata blocks, right? And if you are concerned about the directory names being too revealing, e2image has a -s option which will scramble the directory file names. See the section "RAW IMAGE FILES" in the e2image man page.
Failing that, there probably isn't much we can do, short of having you get a newer version of e2fsprogs, build it with debugging information enabled, and then run it under a debugger so we can get an accurate stack trace. I will note that the stack trace printed by e2fsck doesn't look completely sane, since ext2fs_rb_next() doesn't actually call any C library functions, and far too many of the stack frames don't have symbol names to annotate the addresses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345682 Title: fsck on 24TB ext4 keeps crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1345682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
