Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Steve Fairbairn" <steve@fairbairn-family.com>
To: 'Tony Coffman' <tony@emitony.com>, linux-raid@vger.kernel.org
Subject: RE: Device naming and raid1
Date: Wed, 27 Aug 2008 14:42:55 +0100	[thread overview]
Message-ID: <6974A22713584476AB62E87B84827E37@meanmachine> (raw)
In-Reply-To: <48B554CA.4010804@emitony.com>

> 
> Any idea on my original question?  If I re-add the drive 
> using the /dev/sdc name will I have problems on the next boot 
> when the drive is named /dev/sda?
> 
> Based on my experience with Linux and other software raid 
> implementations, I'm strongly inclined to think that the 
> device naming doesn't matter - the system will scan the 
> drives at boot looking for raid sets and re-assemble them no 
> matter what major and minor numbers or device names are.  I'm 
> not opposed to finding out the hard way but I'd really like 
> to get a definitive answer now because by the time this 
> system is next rebooted I'll probably have long forgotten about this.
> 

Not an expert in any sense of the word, but if the array is being
identified by its UUID and not by a specific list of devices in
mdadm.conf, then the array should assemble fine after a reboot with the
device names having changed.  I recently had a similar situation where I
added a new PCI-E x1 2 port SATA II card, which promptly pushed all my
other sdx devices down two places.  The raid mounted as expected and all
was/is wonderful.

Hope this helps,

Steve.


      parent reply	other threads:[~2008-08-27 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 15:32 Device naming and raid1 Tony Coffman
2008-08-27 11:11 ` David Lethe
2008-08-27 13:21   ` Tony Coffman
2008-08-27 13:31     ` Sujit Karataparambil
2008-08-27 14:08       ` Sujit Karataparambil
2008-08-27 14:46         ` David Greaves
2008-08-27 14:48         ` Tony Coffman
2008-08-27 13:42     ` Steve Fairbairn [this message]

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=6974A22713584476AB62E87B84827E37@meanmachine \
    --to=steve@fairbairn-family.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=tony@emitony.com \
    /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