linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Lee Powell <rlpowell@digitalkingdom.org>
To: linux-raid@vger.kernel.org
Subject: Double mdadm --monitor == hang
Date: Sun, 4 Nov 2007 13:10:37 -0800	[thread overview]
Message-ID: <20071104211037.GA7410@digitalkingdom.org> (raw)


Please cc me on replies; I'm not on the list.

I don't know if this is fixable, or even if it *should* be fixed,
but: summary: shortly after the state of the machine is "2
independent mdadm --monitor instances, resyncing", the
machine totally locks up.  Details follow.

I boot my machine from a USB stick, because the hard drive is
encrypted.  The start up goes something like this:

    mdadm --assemble /dev/md_d0 /dev/sda /dev/sdb /dev/sdc /dev/sdd

    losetup ... /dev/loop0 /dev/md_d0p2

    /bin/mount -o rw -n /dev/loop0 /mnt

    cd /mnt

    /sbin/pivot_root . usb_boot

    exec chroot . /sbin/init $* </dev/console >/dev/console 2>&1

Before it does all that, though, it starts up mdadm --monitor,
because it's got the Debian mdadm package installed, and that's how
that works.

Then in re-runs init after the pivot_root.  The OS on /dev/md_d0p2
also has the Debian mdadm package install, so it also starts mdadm
--monitor.  The two instances have no real way to see each other.

This works fine until a resync is needed; shortly after the state of
the machine is "2 mdadm --monitor instances, resyncing", the machine
totally locks up.

Solved by not starting mdadm --monitor on the USB stick, obviously,
but it took quite a while to figure out.  :(

-Robin

-- 
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

                 reply	other threads:[~2007-11-04 21:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071104211037.GA7410@digitalkingdom.org \
    --to=rlpowell@digitalkingdom.org \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).