Thanks for the hint but I already took care of that as soon as I realized what caused the massive startup delay.
But I think as long as there is no working btrfsck the package should not provide a symlink to btrfsck. If there's need for /sbin/fsck.btrfs it should be symlink pointing to /bin/true instead. At least until a btrfsck is released which doesn't do a full check on clearly unmounted partitions.
Thanks for the hint but I already took care of that as soon as I realized what caused the massive startup delay.
But I think as long as there is no working btrfsck the package should not provide a symlink to btrfsck. If there's need for /sbin/fsck.btrfs it should be symlink pointing to /bin/true instead. At least until a btrfsck is released which doesn't do a full check on clearly unmounted partitions.