The config:

oem@u32:~$ sudo blkid
[sudo] password for oem: 
/dev/sda1: LABEL="dev32" UUID="7b1f4a51-558f-468f-85e0-f815d2f791e1" 
TYPE="ext4" PARTUUID="df9bc38d-01"
/dev/sda4: LABEL="dev64" UUID="7c755ed6-51cc-4b75-88ac-9c75acf82749" 
TYPE="ext4" PARTUUID="df9bc38d-04"
/dev/sda5: LABEL="cur32" UUID="cc94b9dd-3c33-491b-bc40-e4a131dc9b13" 
TYPE="ext4" PARTUUID="df9bc38d-05"
/dev/sda6: LABEL="SAUV" UUID="aa4046be-f906-4ad7-8d2b-61cd4aed332e" TYPE="ext4" 
PARTUUID="df9bc38d-06"
/dev/sdb1: LABEL="LTS32" UUID="9cebceda-bcb5-4ddb-a50c-52f18711594c" 
TYPE="ext4" PARTUUID="b81bb81b-01"
/dev/sdb2: UUID="0a9ca7f0-6eeb-4b21-b70f-670fa600de16" TYPE="swap" 
PARTUUID="b81bb81b-02"
/dev/sdb3: LABEL="lhom" UUID="5d8d1ee1-f5af-40a1-a45d-dbc570808523" TYPE="ext3" 
PARTUUID="b81bb81b-03"


Dumpe2fs:

oem@u32:~$ sudo dumpe2fs /dev/sda1 | grep 'ount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count:              216
Maximum mount count:      -1

oem@u32:~$ sudo dumpe2fs /dev/sda4 | grep 'ount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count:              53
Maximum mount count:      -1

oem@u32:~$ sudo dumpe2fs /dev/sda5 | grep 'ount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count:              82
Maximum mount count:      -1

oem@u32:~$ sudo dumpe2fs /dev/sda6 | grep 'ount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count:              37
Maximum mount count:      -1

oem@u32:~$ sudo dumpe2fs /dev/sdb1 | grep 'ount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count:              99
Maximum mount count:      -1

oem@u32:~$ sudo dumpe2fs /dev/sdb3 | grep 'ount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count:              2
Maximum mount count:      35

( /home , aka lhom, has been created by Feisty installation and is used
till nowadays, so yes its quite old)

------------- the commit says:
added a new mkfs.conf option to turn on the old behavior of random, unexpected, 
time-consuming fscks at boot time. ---------

but there is no mkfs.conf installed across the whole installation,
explaining that the 'random' never happen and cant happen.

So is e2fsprogs has to be blamed as it does not respect that mkfs.conf
commit setting ?



** Changed in: systemd (Ubuntu)
       Status: Incomplete => New

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

Title:
  OS's partitions never fsck'ed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to