Re: Extend BTRFS_IOC_DEVICES_READY for degraded RAID

2015-01-05 Thread Goffredo Baroncelli
On 2015-01-05 12:31, Lennart Poettering wrote: > On Mon, 05.01.15 10:46, Harald Hoyer (har...@redhat.com) wrote: > >> We have BTRFS_IOC_DEVICES_READY to report, if all devices are present, so >> that >> a udev rule can report ID_BTRFS_READY and SYSTEMD_READY. >> >> I think we need a third state h

Re: Extend BTRFS_IOC_DEVICES_READY for degraded RAID

2015-01-05 Thread Austin S Hemmelgarn
On 2015-01-05 06:31, Lennart Poettering wrote: On Mon, 05.01.15 10:46, Harald Hoyer (har...@redhat.com) wrote: We have BTRFS_IOC_DEVICES_READY to report, if all devices are present, so that a udev rule can report ID_BTRFS_READY and SYSTEMD_READY. I think we need a third state here for a degrad

Re: Extend BTRFS_IOC_DEVICES_READY for degraded RAID

2015-01-05 Thread Lennart Poettering
On Mon, 05.01.15 10:46, Harald Hoyer (har...@redhat.com) wrote: > We have BTRFS_IOC_DEVICES_READY to report, if all devices are present, so that > a udev rule can report ID_BTRFS_READY and SYSTEMD_READY. > > I think we need a third state here for a degraded RAID, which can be mounted, > but shoul

Extend BTRFS_IOC_DEVICES_READY for degraded RAID

2015-01-05 Thread Harald Hoyer
We have BTRFS_IOC_DEVICES_READY to report, if all devices are present, so that a udev rule can report ID_BTRFS_READY and SYSTEMD_READY. I think we need a third state here for a degraded RAID, which can be mounted, but should only after a certain timeout/kernel command line params. We also have to