-ARs fails with prior --no-degraded assemblies

Bug #244792 reported by ceg on 2008-07-02
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Dimitri John Ledkov (ex-credativ)

Bug Description

Binary package hint: mdadm


"mdadm --assemble --scan --no-degraded" creates inactive arrays that will not start with a subsequent "mdadm --assemble --scan (--run)"

(N.B. that is what the the udev rules and boot scripts are trying to do instead of using --incremental)

looping error message:
mdadm: SET_ARRAY_INFO failed for /dev/md0: Device or resource busy

ceg (ceg) wrote :

(The array will be crated inactive only if degraded of course)

ceg (ceg) wrote :

Using --incremental (Bug #157981) avoids this bug with ubuntu udev hotplugging.

ceg (ceg) wrote :

When this bug occurs the drives are accessed continously, system hangs.

Dimitri John Ledkov (xnox) wrote :

We are now using --incremental, is this bug still relevant?

Changed in mdadm (Ubuntu):
status: New → Incomplete
ceg (ceg) wrote :

I am not sure, last time I looked (when still using ubuntu), initramfs was not using --incremental to set up the rootfs.

The issue itself may be something worth forwarding/asking to upstream, though.

Launchpad Janitor (janitor) wrote :

[Expired for mdadm (Ubuntu) because there has been no activity for 60 days.]

Changed in mdadm (Ubuntu):
status: Incomplete → Expired
Changed in mdadm (Ubuntu):
status: Expired → Incomplete
status: Incomplete → New
assignee: nobody → Dmitrijs Ledkovs (community) (dle-credativ)

Dmitrijs you marked the bug to new. Which Ubuntu version do you use now and which mdadm version do you use now? Thank you for telling us!

Changed in mdadm (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers