[systemd-devel] no fsck at boot

[Chris Murphy]

On Jun 23, 2014, at 5:06 PM, Mike Gilbert <floppym at gentoo.org> wrote:

> On Mon, Jun 23, 2014 at 6:15 PM, Chris Murphy <lists at colorremedies.com> wrote:
>> But in any case, is there a better way to trigger fsck for ext3/4, and not for XFS and Btrfs, based on some information other than fstab fs_passno? If systemd knew the root file system type before mounting, it could always issue fsck for ext3/4 and never do it for XFS and Btrfs. Maybe it's fs_passno that's become antiquated? Although this may not be generic enough so early in the boot process for systemd to determine file system type without a mount attempt?
>> 
> 
> The btrfs wiki recommends not installing btrfsck as /sbin/fsck.btrfs.
> Instead, it advises to copy/link a no-op command like /bin/true.

Since btrfs-progs 3.14 there is /sbin/fsck.btrfs which does essentially the latter, probably to prevent distributions from doing the former. If you man fsck.btrfs and fsck.xfs they read very much the same "do nothing, successfully".


Chris Murphy