I have over a dozen of filesystems on my OpenBSD server with 12GB DDR3 and several 1.5TB HDDs. All filesystems themselves are generally between 8GB and 64GB in size.

I've noticed that even by following the best practice -- of keeping them so small -- fsck is still very slow on reboot.

What makes fsck so slow? Raw filesystem size? Total number of inodes (iused + ifree)? Number of used inodes? Something else entirely? Any easy way to improve fsck times even further?

  • 1
    fsck is very fast with a few big files. The number of files / inodes is the problem. – Hauke Laging Jun 29 '14 at 19:22
  • slow disk is the problem. – user55518 Jun 29 '14 at 20:11
  • @HaukeLaging, number of iused, ifree, or iused+ifree? Is there any way to decrease the number; why don't they make it easy to decrease it? – cnst Jun 29 '14 at 20:46
  • @cnst I don't know details. It probably depends on the file system, too. ext4 e.g. has a feature for speeding up fsck. And at least one file system (btrfs?) is capable of doing fsck online. – Hauke Laging Jun 29 '14 at 21:05

Any easy way to improve fsck times even further?

@HaukeLaging is right, things can be sped up by changing the density of inodes on the file system. See newfs -i.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.