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 Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1504688 Title: fsck runs on every boot (clean install, single ext4 filesystem) Status in upstart package in Ubuntu: Confirmed Bug description: fsck runs early on *every* boot (and always says "/dev/sda1: clean ...") The system was always shut down using the regular Unity mechanism (Gear->Shut Down...) Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1" shows the date of installation and never changes. This system is a brand new, clean install from the 15.10 beta2 iso, with subsequent updates. I took all the installer defaults, which created a single ext4 file system. Please see attached: bootscreen.png - screen shot of fsck output at start of bootup (from VM window) dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: upstart 1.13.2-0ubuntu16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 15:10:05 2015 InstallationDate: Installed on 2015-10-07 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemJobs: Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1504688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp