Btrfsck problem in Slackware 13.37

ciocead4 · 03-28-2011, 01:21 PM

Hello all,
after updating to the current (13.37) tree I got one systematic error on startup:
...
btrfsck /dev/sdb1
Could not check mount status: Unknown error 4294967294
...
and the system boot is blocked (filesystem is read-only at that moment). This might be related to the latest btrfs-progs update and is mainly due to trying fsck.btrfs on an already mounted partition.
Currently I skipped the error by disabling the fsck completely in rc.S but I'm looking forward to a proper solution if you can guide me.
Thanks,
Daniel

volkerdi · 03-28-2011, 01:33 PM

Quote:

Originally Posted by ciocead4

Hello all,
after updating to the current (13.37) tree I got one systematic error on startup:
...
btrfsck /dev/sdb1
Could not check mount status: Unknown error 4294967294
...
and the system boot is blocked (filesystem is read-only at that moment). This might be related to the latest btrfs-progs update and is mainly due to trying fsck.btrfs on an already mounted partition.
Currently I skipped the error by disabling the fsck completely in rc.S but I'm looking forward to a proper solution if you can guide me.
Thanks,
Daniel

This will be fixed in the next fsck.btrfs script which skips the / partition at boot.

ciocead4 · 03-28-2011, 01:51 PM

Quote:

Originally Posted by volkerdi

This will be fixed in the next fsck.btrfs script which skips the / partition at boot.

Thanks Patrick... BTW, that was a quick answer

willysr · 03-29-2011, 03:16 AM

this is now included in the last update

Code:

a/btrfs-progs-20110327-i486-1.txz: Upgraded.
       In fsck.btrfs script, don't check a filesystem that's mounted as /, even if
       it is mounted read-only. This fix allows using btrfs as a root filesystem,
       but /boot will still need to be on another partition using ext2 (or some
       other filesystem) as btrfs is tricky to boot directly.
       Thanks to gerasimos_h.