On May 20, 2014, at 6:03 PM, Duncan <[email protected]> wrote: > > > I'd actually argue that's functioning as it should, since I see forced > manual intervention in ordered to mount degraded as a FEATURE, NOT A BUG.
Manual intervention is OK for now, when it takes the form of dropping to a dracut shell, and only requires the user to pass mount -o degraded. To mount degraded automatically is worse because within a notification API for user space, it will lead users to make bad choices resulting in data loss. But the needed sequence is fairly burdensome: force shutdown, boot again, use rd.break=premount, then use mount -o degraded, and then exit a couple of times. > [1] dracut: I use it here on gentoo as well, because my rootfs is a multi- > device btrfs and a kernel rootflags=device= line won't parse correctly, > apparently due to splitting at the wrong =, so I must use an initr* > despite my preference for a direct initr*-less boot, and I use dracut to > generate it. rootflags doesn't take a device argument, it only applies to the volume to be mounted at /sysroot, so only one = is needed. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
