On 6/29/20 12:38 PM, Przemek Klosowski via devel wrote:
On 6/27/20 11:40 PM, Tom Seewald wrote:
On Sat, Jun 27, 2020 at 7:32 PM Garry T. Williams
<gtwilliams(a)gmail.com> wrote:
Just a PSA: btrfs raid1 does not have a concept of automatic degraded
mount in the face of a device failure. By default systemd will not
even attempt to mount it if devices are missing.
Is this hopefully seen by upstream as a bug that will be fixed? This
removes the system availability benefits of raid, and I've never
heard of another system that would behave like this, whether that's
zfs, md, or hardware raid.
I agree that it's useful and common for data but booting from degraded
RAID is not universally supported (I think it depends on the boot
manager). Having said that, the flip side of it is that automatic
degraded mount results in a non-redundant system, requiring manual
intervention to restore proper redundancy, anyway.
Oh, and it occurred to me that people probably use raid for two slightly
different reasons: data safety and availability. The first group may
actually prefer (or at least not mind) having to fix the raid before
proceeding.
The second group presumably needs not just automatic degraded mode, but
a system that maintains hot spares and automatically deploys them.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
