On 2018-01-26 09:47, Christophe Yayon wrote:
Hi Austin,
Thanks for your answer. It was my opinion too as the "degraded" seems to be flagged as
"Mostly OK" on btrfs wiki status page. I am running Archlinux with recent kernel on all
my servers (because of use of btrfs as my main filesystem, i need a recent kernel).
Your idea to add a separate entry in grub.cfg with rootflags=degraded is
attractive, i will do this...
Just a last question, i thank that it was necessary to add "degraded" option in
grub.cfg AND fstab to allow boot in degraded mode. I am not sure that only grub.cfg is
sufficient...
Yesterday, i have done some test and boot a a system with only 1 of 2 drive in
my root raid1 array. No problem with systemd, but i added rootflags and fstab
option. I didn't test with only rootflags.
Hmm... I'm pretty sure that you only need degraded in rootflags for a
degraded boot without systemd involved. Not sure about with systemd
involved, though the fact that it worked with systemd at all is
interesting, as last I knew systemd doesn't do any special casing for
BTRFS and just looks at whether all the devices are registered with the
kernel or not.
Also, as far as I know, `degraded` in the mount options won't cause any
change in behavior if there is no device missing, so you're not really
going to be running 'degraded' if you've got all your devices (though
depending on how long it takes to scan devices, you may end up with some
issues during boot when they're technically all present and working).
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
