Bug#780728: systemd: fsck checks root partition and superblock is rewritten on every boot

[Janis Hamme]

Package: systemd
Version: 215-12
Severity: normal

Dear Maintainer,

for some time now I noticed that fsck checks the root partition on every
boot on both my jessie systems, desktop and notebook. As root file
system I use ext4 for both of them.

Relevant part from /etc/fstab:
  # / was on /dev/sda3 during installation
  LABEL=Root    /        ext4    errors=remount-ro 0       1
  LABEL=Home    /home    ext4    errors=remount-ro,noatime 0        1

For some reason systemd rewrites the superblock of my root partition on
every boot:

 Mär 18 11:35:51 laptop systemd-fsck[149]: Root: Superblock last write time
is in the future.
  Mär 18 11:35:51 laptop systemd-fsck[149]: (by less than a day,
probably due
to the hardware clock being incorrectly set).  FIXED.

I have no clue, why systemd assumes the last write time is in the
future. My hardware clock is kept in localtime (timezone Europe/Berlin)
and I manually checked the bios time before boot. The number of mounts
is also resetted when the superblock is rewritten.

/etc/adjtime

  6053.836117 1406826774 0.000000
  1406826774
  LOCAL

Extract from tune2fs -l /dev/sda3 (root partition):

  Filesystem created:       Fri Oct 28 16:24:01 2011
  Last mount time:          Wed Mar 18 11:36:16 2015
  Last write time:          Wed Mar 18 11:35:51 2015
  Mount count:              1
  Maximum mount count:      -1
  Last checked:             Wed Mar 18 11:35:51 2015

In contrast, my home partition has a mount count of 764 and the last
mount time matches the last write time:

  Filesystem created:       Sat Nov 10 18:09:07 2012
  Last mount time:          Wed Mar 18 11:36:16 2015
  Last write time:          Wed Mar 18 11:36:16 2015
  Mount count:              764
  Maximum mount count:      -1
  Last checked:             Sat Nov 10 18:09:07 2012

Another user on the debian-user-german list also reported that fsck runs
on every boot (don't know if the superblock is also rewritten).

I'm not sure when this error appeared first, but I'm quite sure it
wasn't introduced before February this year.



-- Package-specific info:

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (1001, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl             2.2.52-2
ii  adduser         3.113+nmu3
ii  initscripts     2.88dsf-58
ii  libacl1         2.2.52-2
ii  libaudit1       1:2.4-1+b1
ii  libblkid1       2.25.2-5
ii  libc6           2.19-15
ii  libcap2         1:2.24-7
ii  libcap2-bin     1:2.24-7
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.2-4+b1
ii  libkmod2        18-3
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2
ii  libsystemd0     215-12
ii  mount           2.25.2-5
ii  sysv-rc         2.88dsf-58
ii  udev            215-12
ii  util-linux      2.25.2-5

Versions of packages systemd recommends:
ii  dbus            1.8.16-1
ii  libpam-systemd  215-12

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- no debconf information