The "device: clean, 11/65536 files, 12955/262144 blocks" message is what e2fsck prints out when it *skips* an fsck of a filesystem because it's clean. Had it done an fsck, you'd have a message like "device: 11/65536 files (0.0% non-contiguous), 12955/262144 blocks"
Here is an example from a Debian machine: Jun 06 17:35:43 Zia systemd-fsck[726]: SRV has gone 212 days without being checked, check forced. Jun 06 17:35:43 Zia systemd-fsck[715]: HOME has gone 212 days without being checked, check forced. Jun 06 17:35:43 Zia systemd-fsck[717]: /dev/md0: clean, 342/32128 files, 48967/128384 blocks Jun 06 17:35:49 Zia systemd-fsck[726]: SRV: 161336/22892800 files (2.1% non-contiguous), 56809158/91750400 blocks Jun 06 17:35:51 Zia systemd-fsck[715]: HOME: Inode 1828390 extent tree (at level 1) could be shorter. IGNORED. Jun 06 17:35:51 Zia systemd-fsck[715]: HOME: Inode 1828823 extent tree (at level 1) could be shorter. IGNORED. Jun 06 17:35:51 Zia systemd-fsck[715]: HOME: Inode 2103120 extent tree (at level 1) could be narrower. IGNORED. Jun 06 17:36:01 Zia systemd-fsck[715]: HOME: 696295/13056000 files (0.5% non-contiguous), 34370145/52428800 blocks /srv and /home were fsck'd. /dev/md0 was not. So... if it's not causing a boot slowdown: this is how it's supposed to work. If it appears to be causing a boot slowdown: It's probably not actually. Very likely, it's something else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504688 Title: fsck runs on every boot (clean install, single ext4 filesystem) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1504688/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
