[systemd-devel] perform fsck on everyt boot

Andrei Borzenkov arvidjaar at gmail.com
Sat Nov 16 08:31:45 UTC 2019


12.11.2019 13:52, Belisko Marek пишет:
> On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> <lennart at poettering.net> wrote:
>>
>> On Mo, 11.11.19 13:33, Belisko Marek (marek.belisko at gmail.com) wrote:
>> 65;5802;1c
>>> Hi,
>>>
>>> I'm using systemd 234 (build by yocto) and I've setup automount of
>>> sdcard in fstab. This works perfectly fine. But I have seen from time
>>> to time when system goes to emergency mode because sdcard filesystem
>>> (ext4) have an issue and cannot be mounted. I was thinking about
>>> forcing fsck for every boot. Reading manual it should be enough to set
>>> passno (6th column in fstab) to anything higher then 0. I set ti to 2
>>> but inspecting logs it doesn't seems fsck is performed. Am I still
>>> missing something? Thanks.
>>
>> Well, note that ext4's fsck only does an actual file system check
>> every now and then. Hence: how did you determine fsck wasn't started?
>>
>> Do you see the relevant fsck in "systemctl -t service | grep
>> systemd-fsck@"?
> I just saw in log:
> [  OK  ] Found device /dev/mmcblk1p1.
>         Mounting /mnt/sdcard...
> [    8.339072] EXT4-fs (mmcblk1p1): VFS: Found ext4 filesystem with
> invalid superblock checksum.  Run e2fsck?
> [FAILED] Failed to mount /mnt/sdcard.
> 
> and then system goes to emergency mode. I inspect logs but cannot see
> any systemd-fsck process running.

Without seeing /etc/fstab line at the very least anything will be
guesswork. E.g. systemd will not emit fsck dependency if fstype is set
to "auto".


More information about the systemd-devel mailing list