From: Jeff Garzik <jeff@garzik.org>
To: "Gaston, Jason D" <jason.d.gaston@intel.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: AHCI hot replace sdX incrementing
Date: Tue, 10 Apr 2007 05:50:04 -0400 [thread overview]
Message-ID: <461B5DCC.4010208@garzik.org> (raw)
In-Reply-To: <39B20DF628532344BC7A2692CB6AEE070127216E@orsmsx420.amr.corp.intel.com>
Gaston, Jason D wrote:
> When I hot-remove a SATA HD in AHCI mode and then hot-plug the drive
> back in again, the /dev/sdX number changes to the next available number.
> Is this going to be a problem when using a RAID array that includes that
> drive?
Well, it's certainly something you have to deal with. You have to tell
the RAID driver you added a component to the system. Ideally mdadm or
udev should take care of that, but I'm not sure it's all there yet.
In any case, it's a new device so, while inconvenient for some
scenarios, I think it is best to represent a new device with a new
device node. Various entities are still probably holding references to
the old device, and you don't want the system to think that you plugged
in the _same_ device again.
Jeff
prev parent reply other threads:[~2007-04-10 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 17:43 AHCI hot replace sdX incrementing Gaston, Jason D
2007-04-10 9:50 ` Jeff Garzik [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=461B5DCC.4010208@garzik.org \
--to=jeff@garzik.org \
--cc=jason.d.gaston@intel.com \
--cc=linux-ide@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).