[systemd-devel] no fsck at boot

[Reindl Harald]

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


-------------- 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/9023c964/attachment.sig>