[Bug 1083985] Re: fsck routine checks on boot are disabled

[Theodore Ts'o]

What I strongly recommend for long-running enterprise servers is to use
LVM, and then use a customized version of the e2croncheck script:

http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=blob_plain;f=contrib/e2croncheck;h=87204be307c04d2d787dea2ee24e38eababcb373;hb=HEAD

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1083985

Title:
  fsck routine checks on boot are disabled

Status in “e2fsprogs” package in Ubuntu:
  Invalid

Bug description:
  After installation of Ubuntu 12.04.1 I've noticed that periodical fsck check during boot time never runs, as it was when I was using Ubuntu 10.04. I checked my old 10.04 installation with 'tune2fs -l' and found that root partition had 'Maximum mount count' = 23 and home partition - 35 (both are ext4).
  'tune2fs -l' on 12.04.1 shows 'Maximum mount count' = -1 on all partitions: /boot (ext3), / and /home (ext4). That means that fsck checks will never run. 'Check interval' is also set to 0 on all volumes.
  If this decision was made for the sake of fast boot up, I presume that data integrity have the maximum priority. While this decision is somewhat meaningful on laptops to preserve the battery, but on desktops and servers it is not good at all. Also tune2fs man says that it is strongly recommended that either mount-count-dependent or time-dependent checking must be enabled.
  As I found no info indicating that this behaviour is intentional, I suppose that this is a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1083985/+subscriptions