All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Konstantin Olchanski <olchansk@sam.triumf.ca>
Cc: Dave Jiang <djiang@mvista.com>,
	AndyLiebman@aol.com, linux-raid@vger.kernel.org
Subject: Re: udev and mdadm -- I'm lost
Date: Wed, 16 Nov 2005 12:38:20 -0500	[thread overview]
Message-ID: <437B6E8C.9000100@tmr.com> (raw)
In-Reply-To: <20051109075732.GB7815@sam.triumf.ca>

Konstantin Olchanski wrote:

>On Tue, Nov 08, 2005 at 04:40:23PM -0700, Dave Jiang wrote:
>  
>
>>>I see there is an mdadm  --auto option now...
>>>      
>>>
>>Just use --auto or --auto=yes and it should take care of the device node 
>> creations. I have a /etc/mdadm.conf so I just do:
>>mdadm -As --auto=yes and it brings everything up over udev.
>>    
>>
>
>I face a similar problem each time I use KNOPPIX to revive a non-booting
>server. It always takes me 10-20 minutes to figure out the right
>mdadm incantation to start the md devices. It does not help that mdadm
>wants an /etc/mdadm.conf which is on an md device itself, unaccessible.
>  
>
Hate to say it, that's a reward of a poor config choice and should be fixed.

>I wish there were a simple command to find and start all md devices, something
>along the lines of:
>
>mdadm --please-find-and-start-all-my-md-devices-please-please-please
>or
>mdadm --start-all, or whatever.
>
>  
>


-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  reply	other threads:[~2005-11-16 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 23:21 udev and mdadm -- I'm lost AndyLiebman
2005-11-08 23:39 ` Sandro Dentella
2005-11-08 23:40 ` Dave Jiang
2005-11-09  7:57   ` Konstantin Olchanski
2005-11-16 17:38     ` Bill Davidsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-08 23:50 AndyLiebman

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=437B6E8C.9000100@tmr.com \
    --to=davidsen@tmr.com \
    --cc=AndyLiebman@aol.com \
    --cc=djiang@mvista.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=olchansk@sam.triumf.ca \
    /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 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.