The ebuild doesn't add a symlink from btrfsck to fsck.btrfs. If a btrfs volume is set to be checked on boot in fstab, the system tries to execute fsck.btrfs but fails since it can't be found.
Well, it seems like this symlink was omitted on purpose. If you look into the btrfs-progs ebuilds you will find the following comment in src_install():
# fsck will segfault if invoked at boot, so do not make this link
#dosym btrfsck /sbin/fsck.btrfs
Of course you can maybe check if this is still true for latest btrfsck by creating the symlink manually and make the system doing a fsck on the next reboot (shutdown -F -r now).
Reassigning to the btrfs-progs maintainer as he might shed some light on this.
I just booted with the symlink and fsck.btrfs seemed to have worked just fine.
I now had the time to do some testing with a btrfs-partition and there's still a (maybe small) problem. btrfsck doesn't accept any commandline options other than the partition to check which results in error messages when fsck.btrfs gets invoked at boot (Could not open -p).
You're right. The problem is still there. I guess it's up to upstream to fix that
Hey guys, yes, I had the symlink there originally, but because of the segfault, I removed it. Better at this point to do manual fsck's if you need to. But if upstream improves this, feel free to reopen this bug.
Btrfs is not *supposed* to need regular fsck's anyway, AFAIK.
*** Bug 327663 has been marked as a duplicate of this bug. ***
I had created the symlink and fs check at boot went without errors (used systemd as init system).