Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Andrew Klaassen <clawsoon@yahoo.com>
To: Iordan Iordanov <iordan@cdf.toronto.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Preventing a RAID device from starting until all disks are ready
Date: Thu, 14 Oct 2010 12:31:39 -0700 (PDT)	[thread overview]
Message-ID: <5533.55464.qm@web65403.mail.ac4.yahoo.com> (raw)
In-Reply-To: <4CB7292A.6040209@cdf.toronto.edu>

--- On Thu, 10/14/10, Iordan Iordanov <iordan@cdf.toronto.edu> wrote:

> We have iscsi targets for drives in our array, and we make
> sure that we've logged into all 30 of our drives before we
> continue to enable mdadm (we literally count the number of
> iscsi sessions open). You can try counting the number of
> block devices present (in /dev/block) that match a certain
> pattern, or perhaps your fiber channel driver offers an even
> more convenient facility in /dev.

It seems like the simplest way to do this would be to have two mdadm.conf files; one for the root arrays that need to come up right away, one for the FC/iSCSI arrays that need to wait.

Is either of these ideas:

 - run two "mdadm --monitor" processes simultaneously, one for each set of arrays, or

 - specify two config file arguments to "mdadm --monitor"

...possible?

Thanks.

Andrew





  reply	other threads:[~2010-10-14 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 15:36 Preventing a RAID device from starting until all disks are ready Andrew Klaassen
2010-10-14 16:00 ` Iordan Iordanov
2010-10-14 19:31   ` Andrew Klaassen [this message]
2010-10-15  1:54   ` Neil Brown
2010-10-15  8:19     ` Jon Hardcastle
  -- strict thread matches above, loose matches on Subject: below --
2010-10-14 17:00 Andrew Klaassen
     [not found] <505206.15544.qm@web65407.mail.ac4.yahoo.com>
2010-10-18 18:00 ` Iordan Iordanov

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=5533.55464.qm@web65403.mail.ac4.yahoo.com \
    --to=clawsoon@yahoo.com \
    --cc=iordan@cdf.toronto.edu \
    --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