FS#29182 - [btrfs-progs] fsck.btrfs missing error when building images
Attached to Project:
Arch Linux
Opened by John (graysky) - Thursday, 29 March 2012, 20:56 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 29 March 2012, 23:17 GMT
Opened by John (graysky) - Thursday, 29 March 2012, 20:56 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 29 March 2012, 23:17 GMT
|
Details
Description: mkinitcpio reports the following when I attempt
to build an image. I don't know if this is the fault of
btrfs-progs, or of mkinitcpio.... or of me :)
$ sudo mkinitcpio -p linux ==> Building image from preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 3.3.0-1-ARCH -> Parsing hook: [base] -> Parsing hook: [udev] -> Parsing hook: [autodetect] -> Parsing hook: [pata] -> Parsing hook: [scsi] -> Parsing hook: [sata] -> Parsing hook: [filesystems] -> Parsing hook: [usbinput] -> Parsing hook: [fsck] ==> ERROR: file not found: `fsck.btrfs' ==> WARNING: No fsck helpers found. fsck will not be run on boot. ... I have [testing] enabled and am up-to-date. Additional info: * package version(s) testing/btrfs-progs 0.19.20120328-1 [installed] core/mkinitcpio 0.8.5-1 [installed] Steps to reproduce: Boot or chroot into a btrfs root filesystem, then attempt to run mkinitcpio. |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 29 March 2012, 23:17 GMT
Reason for closing: Not a bug
Additional comments about closing: btrfsck doesn't play well with the fsck helper
Thursday, 29 March 2012, 23:17 GMT
Reason for closing: Not a bug
Additional comments about closing: btrfsck doesn't play well with the fsck helper
Regardless of what this utility does, it doesn't support being called by the fsck helper yet, which is what mkinitcpio relies on. It would be useful to find out from upstream what their long term plan is -- if btrfsck will one day be called fsck.btrfs and integrate with all the proper flags of a standard fsck helper.
I will request that this report get closed as it doesn't seem to be any bug or problem with our packages.