On Tue, 20 May 2014 18:51:26 -0600
Chris Murphy li...@colorremedies.com wrote:
On May 20, 2014, at 6:03 PM, Duncan 1i5t5.dun...@cox.net 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
On 05/19/2014 02:54 AM, Chris Murphy wrote:
Summary:
It's insufficient to pass rootflags=degraded to get the system root
to mount when a device is missing. It looks like when a device is
missing, udev doesn't create the dev-disk-by-uuid linkage that then
causes systemd to change the device
On Wed, May 21, 2014 at 12:00:24AM +0200, Goffredo Baroncelli wrote:
On 05/19/2014 02:54 AM, Chris Murphy wrote:
Summary:
It's insufficient to pass rootflags=degraded to get the system root
to mount when a device is missing. It looks like when a device is
missing, udev doesn't create
Hugo Mills posted on Tue, 20 May 2014 23:26:09 +0100 as excerpted:
On Wed, May 21, 2014 at 12:00:24AM +0200, Goffredo Baroncelli wrote:
On 05/19/2014 02:54 AM, Chris Murphy wrote:
It's insufficient to pass rootflags=degraded to get the system root
to mount when a device is missing. It looks
On May 20, 2014, at 6:03 PM, Duncan 1i5t5.dun...@cox.net 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
Summary:
It's insufficient to pass rootflags=degraded to get the system root to mount
when a device is missing. It looks like when a device is missing, udev doesn't
create the dev-disk-by-uuid linkage that then causes systemd to change the
device state from dead to plugged. Only once plugged,
