touch-packages team mailing list archive

[dino99 <1413554@xxxxxxxxxxxxxxxxxx>]

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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413554

Title:
  OS's partitions never fsck'ed

Status in systemd package in Ubuntu:
  New

Bug description:
  In the past 3 months the /home data partition [ext3] has been fsck'ed as expected (every 35 mounts) on that vivid i386 booted with systemd (systemd-sysv installed). But none of the 3 other OS partitions [ext4] have been fsck'ed, which seems scary. So systemd seems not dealing with all the cases.
  I have use 'shutdown -R now' to expect forcing fsck on the next boot, but only /home is checked.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-3ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  BootDmesg: (Nothing has been logged yet.)
  CurrentDesktop: GNOME
  Date: Thu Jan 22 11:54:22 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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