[systemd-devel] Second (erroneous) check of rootfs?

Nikolai Zhubr n-a-zhubr at yandex.ru
Wed Jan 7 16:36:41 PST 2015


I'm not quite sure if it belongs to systemd or rather dracut or even 
opensuse bugtracker... Please feel free to redirect me as appropriate.

Below is a fragment of jounal of one boot of opensuse 13.2, irrelevant 
parts replaced by dots to compact it a bit.
In short, AFAICS:

1. In initrd, root disk is found as "uuid-588d..." and successfully fsck'ed.

2. Next, it is mounted read-only to /sysroot. It should here be noted 
that mounting read-only AFAIK is no guarantee that no modifications can 
happen to the underlying media (E.g. some filesystems might start 
background recovery even in read-only state, including IIRC ext3+).

3. Before remounting root fs to / as read-write, a second fsck is 
performed. I consider this probably unwise because:
-- it is unnecessary and just increases boot time,
-- if root fs is in some trouble then fsck'ing it while still mounted 
might break it even harder in some cases (depending on fs type and 

Thank you,
----------------- cut -----------------
01:54:58 systemd[1]: Starting File System Check on 
01:54:59 systemd-fsck[334]: /dev/md0: clean, 130091/1313280 files, 
1176795/5242880 blocks
01:54:59 systemd[1]: Mounting /sysroot...
01:54:59 systemd[340]: Executing: /bin/mount -n -t auto -o ro 
/dev/disk/by-uuid/588d9a9c-4c4e-4400-9e2b-a79f5fce670e /sysroot
01:54:59 kernel: EXT4-fs (md0): mounted filesystem with ordered data 
mode. Opts: (null)
01:54:59 systemd[1]: Mounted /sysroot.
01:55:12 systemd-fsck[432]: /dev/md0: clean, 130091/1313280 files, 
1176795/5242880 blocks
01:55:12 systemd[1]: Starting Remount Root and Kernel File Systems...
01:55:12 kernel: EXT4-fs (md0): re-mounted. Opts: noacl
----------------- cut -----------------

More information about the systemd-devel mailing list