All of lore.kernel.org
 help / color / mirror / Atom feed
* /dev/md/xxx sporadically unavailable after mdadm --assemble /dev/md/xxx
@ 2015-03-15  7:42 Andrei Borzenkov
  0 siblings, 0 replies; only message in thread
From: Andrei Borzenkov @ 2015-03-15  7:42 UTC (permalink / raw)
  To: linux-raid

I hit this when running test suite that is using Linux MD over loop
devices. Sporadically it fails to mount raid after mdadm --assembly
with 

mdadm: array /dev/md/mdraid10_raid1_6 started.
mdadm: stopped /dev/md/mdraid10_raid1_6
mdadm: /dev/md/mdraid10_raid1_6 has been started with 6 drives.
mount: special device /dev/md/mdraid10_raid1_6 does not exist

How naive is the assumption that when "mdadm --assemble" returns
devices are available? Should every use of mdadm be now followed by
waiting for device?

Code is simply

                xmdraid*)
                    mdadm --assemble /dev/md/"${fs}_$NDEVICES" "${LODEVICES[@]}"
                    sleep 1
                    mount -t "$MOUNTFS" "${MOUNTDEVICE}" "$MNTPOINTRO" -o ${MOUNTOPTS}${SELINUXOPTS}ro ;;


but apparently even one second wait is not enough. But where is the
limit?

Of course when you look after test failure all devices are there.

Using mdadm 3.3.1 on openSUSE 13.2.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-03-15  7:42 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-15  7:42 /dev/md/xxx sporadically unavailable after mdadm --assemble /dev/md/xxx Andrei Borzenkov

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.