> 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
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
>
#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
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:
>
>
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:
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
6 matches
Mail list logo
