Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

pogeymanz · 2013-02-04 18:30:10

Can I just symlink btrfsck to it?

mariusmeyer · 2013-02-04 18:44:28

"Mad"? What is the problem exactly? I don't have any problem with it. Just set the pass option in fstab to 0. Btrfsck cannot yet actually repair most problems anyway, at least that's my understanding of it.

ewaller · 2013-02-04 19:02:45

Nice anthropomorphism

Where does the btrfs volume get mounted? Is it root?

falconindy · 2013-02-04 19:09:21

No, you cannot symlink it. disable fsck in /etc/fstab. btrfs volumes do not require religious fsck'ing after N mounts like journaled filesystems do.

Last edited by falconindy (2013-02-04 19:09:45)

WorMzy · 2013-02-04 19:13:43

No, don't symlink btrfsck. It's not designed to be used as a fsck.* tool.

I don't see what systemd's got to do with anything. mkinitcpio will tell you that it can't find fsck.btrfs, and I guess the ramdisk will reiterate that if you have the fs_passno set to 1 or 2 for a btrfs filesystem in fstab, but neither of these have anything to do with systemd.

pogeymanz · 2013-02-04 19:21:58

Systemd tried to fsck my partitions when I booted and it gave some error that it couldn't find fsck.btrfs. My root partition is btrfs, as are most of my others (not boot).

Thanks for the info guys.

tomegun · 2013-02-05 09:20:36

In case it was not clear: systemd is trying to fsck your partition because you told it to in your fstab, just set the fs_passno (the sixth field) for your btrfs entries to 0.

R00KIE · 2013-02-05 14:20:19

falconindy wrote:

No, you cannot symlink it. disable fsck in /etc/fstab. btrfs volumes do not require religious fsck'ing after N mounts like journaled filesystems do.

The default configuration shipped with e2fsprogs does not enable periodic fsck for newly formatted filesystems, so I guess journaled filesystems do not need to be religiously fscked after N mounts / M days although 'man tune2fs' says otherwise.

ANOKNUSA · 2013-02-05 17:37:53

I don't think any of these actually need to be checked to operate properly; it's just a matter of redundancy/contingency. Periodic filesystem checks are one of those things most folks don't think of unless they already have a problem, so the system is set to check every so often (21 mounts?) just in case.

WorMzy · 2013-02-05 17:43:44

Indeed. These filesystems generally know when the need fscking, the n mounts thing seems like more of a safety net, which I guess is no longer deemed necessary.

Arch Linux

#1 2013-02-04 18:30:10

Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#2 2013-02-04 18:44:28

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#3 2013-02-04 19:02:45

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#4 2013-02-04 19:09:21

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#5 2013-02-04 19:13:43

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#6 2013-02-04 19:21:58

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#7 2013-02-05 09:20:36

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#8 2013-02-05 14:20:19

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#9 2013-02-05 17:37:53

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

#10 2013-02-05 17:43:44

Re: Systemd gets mad because it can't find a 'fsck.btrfs' on boot.

Board footer