On 01/07/2015 08:16 AM, The Wanderer wrote: > On 01/07/2015 at 08:39 AM, ~Stack~ wrote: > [snip] >> However, I >> *have* read the man page and the man page for fstab says "If the >> sixth field is not present or zero, a value of zero is returned and >> fsck will assume that the filesystem does not need to be checked." >> Therefore, I am explicitly telling systemd-fsck to buggeroff and not >> check. I as the owner of the device have acknowledged and assumed all >> the risk for not running fsck on my drive. The fact that it is >> /still/ doing it against my wishes is what annoys me. > > According to my understanding, this field is not in fact a global > boot-time-fsck override, which you seem to be expecting it to be. > > There are actually (at least) two ways in which fsck can be triggered at > boot time: by the automatic iterate-through-the-fstab is-a-fsck-needed > procedure, which reads and respects this field (because it's iterating > through fstab anyway), and in response to a failed mount attempt, which > I believe ignores this field (because the fsck was invoked in a way > which has nothing to do with fstab - just as would happen if you invoked > fsck manually).
Hrm. Ok. I learned something today. :-) I don't know why, but I really thought that meant that fsck wouldn't check at all if the sixth field was 0. Thanks! ~Stack~
signature.asc
Description: OpenPGP digital signature
