There are plenty of people who *are* able to check file systems larger than
16TB. So talking about it in terms "that problem" doesn't make much sense.
There is a known issue where if you are using a huge number of hard links (if
you are using a backup solution which uses hard links and a huge number of
parallel directory hierarchies) e2fsck uses a large amount of memory. I don't
know if that's what you are doing, but if that's what you are doing, it
wouldn't surprise me if you are running out of memory. You should have gotten
an explicit "you ran out of memory" error instead of a seg fault, though.
There is a way you can use scratch files for some of the data structures that
e2fsck needs to track all of the hard links; see the
"The [scratch_files] Stanza" section in the e2fsck.conf. However, this is
going to be *SLOW*. The primary use of this was for people who were using
32-bit systems and who didn't have the address space for the memory
requirements for large file systems with a large number of hard links. You
may be better off just trying to configure our swap space. (All of this is
assuming the problem is that the file system has a very large number of hard
link farms. Have you confirmed that when you configured 25GB of swap, that the
system actually used that amount of swap)?
--
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
