[systemd-devel] no fsck at boot

[Reindl Harald]

Am 09.06.2014 21:26, schrieb Alexander E. Patrakov:
> 10.06.2014 00:57, Reindl Harald wrote:
>>
>> Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
>>> 10.06.2014 00:04, Reindl Harald wrote:
>>>>
>>>> Am 09.06.2014 17:05, schrieb Colin Guthrie:
>>>>> 'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
>>>>>> "touch /forcefsck" leads in deprecated warnings but in fact at least
>>>>>> on Fedora 19 *you need it* because the fsck don't happen otherwise
>>>>>>
>>>>>> for sure, the last reboot of the machine below complaind too
>>>>>> so why don't it happen at boot?
>>>>>
>>>>> Via what mechanism did you trigger the fsck at boot (other than
>>>>> /forcefsck)? e.g. did you pass fsck.mode=force on the kernel command
>>>>> line (as the deprecated warning suggests)? Did this not trigger things
>>>>> correctly?
>>>>
>>>> uhm you stripped the relevant part of my message
>>>>
>>>> * the filesystem has reached the time for next fsck
>>>> * the kernel says it's time
>>>> * before systemd did happended automatically
>>>> * that is why ext4 defines the fsck interval at all
>>>
>>> Please paste your /etc/fstab file. If it has "0 0" as the last two fields, then, of course, systemd will not call
>>> fsck. If there are different numbers there, sure, let's debug.
>>>
>>> Also, now the entity that is supposed to check your root filesystem is dracut. Are you using it? Does the problem
>>> go away if you regenerate your initramfs?
>>
>> i know how to deal with fstab and column 6 is not zero as well
>> as the initramfs is regenrated all the time because kernel
>> updates which are *the reason* for reboots on servers at all
>>
>> what disturbs me is they warning about "touch /forcefsck" while
>> it's currently the *only* option to trigger a recommended fsck
>> at boot on a remote-server (and no add kernel params for that
>> in the grub-config and remove them after is not a sane way for
>> sysadmins maintaining 10,20,30 remote servers)
>>
>> UUID=209aeed4-95bd-4eb0-bdfa-fb346b603ce9 /boot ext4 defaults 0 1
>> UUID=22f62744-8fd7-4090-aff8-b35ef38b4b74 / ext4
>> defaults,commit=5,inode_readahead_blks=128,noatime,nodiratime,noquota 0 1
>> UUID=0b95905b-02c5-444b-af9e-7615cabebb38 /mnt/data ext4
>> defaults,commit=5,inode_readahead_blks=128,noatime,nodiratime,noquota,nosuid  0 2
>>
> 
> OK.
> 
> Let's try eliminating some more reasons why fsck can be skipped.
> 
> 1. The root filesystem is mounted read-write at boot [but note that this doesn't explain failures to check other
> filesystems]
> 2. The generator did not run for some unknown reason.
> 3. Some other error that got hopefully logged.
> 
> Could you please attach the output of:
> 
> ls -lR /run/systemd/generator
> journalctl -b
> 
> Also, could you please try replacing some non-critical UUID=... lines (e.g. for /boot) in your fstab by direct
> device references of the form /dev/disk/by-uuid/209aeed4-95bd-4eb0-bdfa-fb346b603ce9 or even /dev/mdX, just to see
> if that's UUID who triggers the bug for you? To avoid getting an inaccessible server if that misfires, you can also
> append nofail to the options for /boot

systemd even pretends it does the fsck, i have nothing more to say
on that topic except remove the deprecation warning and output
the volume-label at least additionally to the UUID

[root at localhost:~]$ journalctl -b | grep "File System"
Jun 08 14:51:15 localhost systemd[1]: Starting Local File Systems.
Jun 08 14:51:15 localhost systemd[1]: Reached target Local File Systems.
Jun 08 14:51:16 localhost systemd[1]: Starting Initrd Root File System.
Jun 08 14:51:16 localhost systemd[1]: Reached target Initrd Root File System.
Jun 08 14:51:16 localhost systemd[1]: Starting Initrd File Systems.
Jun 08 14:51:16 localhost systemd[1]: Reached target Initrd File Systems.
Jun 08 14:51:19 localhost systemd[1]: Started File System Check on Root Device.
Jun 08 14:51:19 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
Jun 08 14:51:19 localhost systemd[1]: Started Remount Root and Kernel File Systems.
Jun 08 14:51:19 localhost systemd[1]: Starting Local File Systems (Pre).
Jun 08 14:51:19 localhost systemd[1]: Reached target Local File Systems (Pre).
Jun 08 14:51:20 localhost systemd[1]: Starting File System Check on
/dev/disk/by-uuid/209aeed4-95bd-4eb0-bdfa-fb346b603ce9...
Jun 08 14:51:20 localhost systemd[1]: Started File System Check on
/dev/disk/by-uuid/209aeed4-95bd-4eb0-bdfa-fb346b603ce9.
Jun 08 14:51:20 localhost systemd[1]: Starting File System Check on
/dev/disk/by-uuid/0b95905b-02c5-444b-af9e-7615cabebb38...
Jun 08 14:51:21 localhost systemd[1]: Started File System Check on
/dev/disk/by-uuid/0b95905b-02c5-444b-af9e-7615cabebb38.
Jun 08 14:51:21 localhost systemd[1]: Starting Local File Systems.
Jun 08 14:51:21 localhost systemd[1]: Reached target Local File Systems.

[root at localhost:~]$ journalctl -b | grep "e2fsck"
Jun 08 14:51:19 localhost kernel: EXT4-fs (md127): warning: checktime reached, running e2fsck is recommended
Jun 08 14:51:20 localhost kernel: EXT4-fs (md126): warning: checktime reached, running e2fsck is recommended
Jun 08 14:51:21 localhost kernel: EXT4-fs (md125): warning: checktime reached, running e2fsck is recommended

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140609/a33e9b46/attachment.sig>