Bug#947811: systemd: don't check *mounted* filesystems by default
> If you want to fsck/mount your partitions manually via a custom script that is run before init, then I would set passno to 0. I've since masked the job that systemd uses to run fsck. It's still a bug because if somebody forgets and leaves a filesystem mounted read-write in the emergency shell (fixing anything other than fsck problems in the emergency shell usually requires mounting things read-write), the same problem happens and no custom script is involved.
Bug#947811: systemd: don't check *mounted* filesystems by default
Am 12.01.20 um 16:59 schrieb Joshua Hudson: > #need_real_mtab > /dev/mapper/isw_cfbejbfeib_Volume11 / ext3 defaults 0 1 > /dev/mapper/isw_cfbejbfeib_Volume12 none swap sw 0 0 > none /tmp tmpfs defaults 0 0 > /dev/mapper/isw_cfbejbfeib_Volume13 /home ext3 defaults 0 2 > /dev/mapper/isw_cfbejbfeib_Volume14 /home/joshua/imagefiles ext3 defaults 0 3 You are instructing systemd to run fsck by setting passno to a value greater zero. See the man page of systemd-fsckd. If you want to fsck/mount your partitions manually via a custom script that is run before init, then I would set passno to 0. signature.asc Description: OpenPGP digital signature
Bug#947811: systemd: don't check *mounted* filesystems by default
#need_real_mtab /dev/mapper/isw_cfbejbfeib_Volume11 / ext3 defaults 0 1 /dev/mapper/isw_cfbejbfeib_Volume12 none swap sw 0 0 none /tmp tmpfs defaults 0 0 /dev/mapper/isw_cfbejbfeib_Volume13 /home ext3 defaults 0 2 /dev/mapper/isw_cfbejbfeib_Volume14 /home/joshua/imagefiles ext3 defaults 0 3 /dev/sr0 /media/cdrom iso9660 noauto,ro,user 0 0 /dev/sr1 /media/cdrom1 iso9660 noauto,ro,user 0 0
Bug#947811: systemd: don't check *mounted* filesystems by default
Am 31.12.19 um 17:54 schrieb Joshua Hudson: > I had to use fsck.mode=force to get it to reproduce on the very next > boot. Otherwise, it reproduces sporadically. I don't want to > deliberately crash the system badly enough to get it to really need to > fsck the next boot. > > Reduced logs: > > Dec 31 08:42:05 nova kernel: Command line: BOOT_IMAGE=Lin ro > root=/dev/mapper/isw_cfbejbfeib_Volume11 video=960x540 fsck.mode=force > Dec 31 08:42:05 nova kernel: Kernel command line: BOOT_IMAGE=Lin ro > root=/dev/mapper/isw_cfbejbfeib_Volume11 video=960x540 fsck.mode=force > Dec 31 08:42:05 nova kernel: Adding 33554428k swap on > /dev/mapper/isw_cfbejbfeib_Volume12. Priority:-2 extents:1 > across:33554428k FS > Dec 31 08:42:08 nova systemd[1]: Condition check resulted in > /dev/mapper/isw_cfbejbfeib_Volume12 being skipped. > Dec 31 08:42:08 nova dmraid-activate[579]: ERROR: Cannot retrieve RAID > set information for isw_cfbejbfeib_Volume1 > Dec 31 08:42:08 nova dmraid-activate[572]: ERROR: Cannot retrieve RAID > set information for isw_cfbejbfeib_Volume1 > Dec 31 08:42:09 nova systemd[1]: Condition check resulted in > /dev/mapper/isw_cfbejbfeib_Volume13 being skipped. > Dec 31 08:42:09 nova systemd[1]: Starting File System Check on > /dev/mapper/isw_cfbejbfeib_Volume13... > Dec 31 08:42:09 nova systemd[1]: Started File System Check on > /dev/mapper/isw_cfbejbfeib_Volume13. > Dec 31 08:42:15 nova systemd[1]: Condition check resulted in > /dev/mapper/isw_cfbejbfeib_Volume14 being skipped. > Dec 31 08:42:15 nova systemd[1]: Starting File System Check on > /dev/mapper/isw_cfbejbfeib_Volume14... > Dec 31 08:42:15 nova systemd[1]: Started File System Check on > /dev/mapper/isw_cfbejbfeib_Volume14. > > e2fsck complains on the console about Volume14 being mounted, but > there's no trace in the logs. > > Note that I have to mount everything in /sbin/init before handing off > to systemd because otherwise it waits for the raid controller > containing / to come up so it can mount it read-write (makes no > sense--/ is already up by definition). > Can you attach your /etc/fstab please? signature.asc Description: OpenPGP digital signature
Bug#947811: systemd: don't check *mounted* filesystems by default
Control: tags -1 + moreinfo Am 31.12.19 um 03:29 schrieb Joshua: > Package: systemd > Version: 241-7~deb10u2 > Severity: important > > systemd tries to fsck mounted filesystems by default. Please provide a verbose debug log from the complete boot where this is happening: https://freedesktop.org/wiki/Software/systemd/Debugging/#index1h1 signature.asc Description: OpenPGP digital signature
Bug#947811: systemd: don't check *mounted* filesystems by default
Package: systemd Version: 241-7~deb10u2 Severity: important systemd tries to fsck mounted filesystems by default. Don't ever try to fsck a filesystem mounted read/write. All that does is trash things. If somebody left a filesystem mounted rw on the emergency shell, best to not check it this boot. -- Package-specific info: -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) (wrong!) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.53-4 ii libapparmor1 2.13.2-10 ii libaudit11:2.8.4-3 ii libblkid12.33.1-0.1 ii libc62.28-10 ii libcap2 1:2.25-2 ii libcryptsetup12 2:2.1.0-5+deb10u2 ii libgcrypt20 1.8.4-5 ii libgnutls30 3.6.7-4 ii libgpg-error01.35-1 ii libidn11 1.33-2.2 ii libip4tc01.8.2-4 ii libkmod2 26-1 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.4-1 ii libmount12.33.1-0.1 ii libpam0g 1.3.1-5 ii libseccomp2 2.3.3-4 ii libselinux1 2.8-1+b1 ii libsystemd0 241-7~deb10u2 ii mount2.33.1-0.1 ii util-linux 2.33.1-0.1 Versions of packages systemd recommends: ii dbus 1.12.16-1 ii libpam-systemd-apt-holepunch [libpam-systemd] 1 Versions of packages systemd suggests: ii policykit-10.105-25 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.133+deb10u1 ii udev 241-7~deb10u2 -- Configuration Files: /etc/systemd/journald.conf changed: [Journal] Storage=none ForwardToSyslog=1 -- no debconf information
