Ok, thought of checking it in somewhere.
->blueprints?
--
mounts fail because degraded raid is not beeing started
https://bugs.launchpad.net/bugs/496461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
If you have written a spec, there is no need for a bug to be opened
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
mounts fail because degraded raid is not beeing started
https://bugs.launchpad.net/bugs/496461
You received this bug notification because you are a member of Ubun
As "mountall" already has the "waiting for device" functionality,
linking this to https://wiki.ubuntu.com/ReliableRaid that was updated
with email discussion and made to match a SpecTemplate.
** Changed in: mountall (Ubuntu)
Status: Invalid => New
--
mounts fail because degraded raid is n
On Mon, 2009-12-14 at 11:11 +, ceg wrote:
> Ok, mdadm would need a way to be invoked after a hotplug timeout.
>
There's no such thing as a "hotplug timeout"
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
mounts fail because degraded raid is not beeing started
https://bugs.launchpad.net/
> There's no such thing as a "hotplug timeout"
Hmm, then we would need a watchdog like thing that checks if necessary
md devices have come up for a while? (Degrading the array after a
timout, but otherwile similar to what mountall is doing?)
--
mounts fail because degraded raid is not beeing sta
Ok, mdadm would need a way to be invoked after a hotplug timeout.
Do you have a recommendation how to do this right in the upstart
perspective/configuration, maybe?
--
mounts fail because degraded raid is not beeing started
https://bugs.launchpad.net/bugs/496461
You received this bug notificati
mountall isn't involved here (and I already see many bugs open against
mdadm about this)
As soon as mdadm activates the raid device, mountall will try and mount
it - the problem is the device isn't activated
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
mounts fail because d
