On Mon, Jun 29, 2020 at 10:38 AM Przemek Klosowski via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> 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. It's a really good point. > > In other words, we still need a mechanism to notify and ensure that the > raid is rebuilt---too much automation could lead people into false sense > of security. I think there is a notification in GNOME Shell in case of mdadm degraded state. And it's appropriate to expect parity for the Btrfs case. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
