From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Richard Scobie <richard@sauce.co.nz>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Reallocating sd device
Date: Mon, 09 Jun 2008 14:54:43 -0500 [thread overview]
Message-ID: <1213041283.3508.66.camel@localhost.localdomain> (raw)
In-Reply-To: <484D8935.70905@sauce.co.nz>
On Tue, 2008-06-10 at 07:49 +1200, Richard Scobie wrote:
> Testing a 16 SATA drive (/dev/sd[c-r]1), md RAID, with drives installed
> in a hotswap SAS/SATA enclosure.
>
> Failed out /dev/sdd1, ejected the drive from the enclosure, reinserted
> it and the system added it back as /dev/sds:
>
> Jun 9 11:24:37 flash2 kernel: mptsas: ioc0: removing sata device,
> channel 0, id 30, phy 5
> Jun 9 11:24:37 flash2 kernel: sd 4:0:1:0: [sdd] Synchronizing SCSI cache
>
> Jun 9 11:24:37 flash2 kernel: sd 4:0:1:0: [sdd] Result:
> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
>
> Jun 9 11:26:38 flash2 kernel: mptsas: ioc0: attaching sata device,
> channel 0, id 30, phy 5
>
> Jun 9 11:26:38 flash2 kernel: scsi 4:0:17:0: Direct-Access ATA
> WDC WD7500AYYS-0 4G30 PQ: 0 ANSI: 5
>
> Jun 9 11:26:38 flash2 kernel: sd 4:0:17:0: [sds] 1465149168 512-byte
> hardware sectors (750156 MB)
>
> Rebooting shows the offline drive back as /dev/sdd.
>
> Is there a safe, (OK to do on a mounted, active array), way of changing
> the sds back to sdd, prior to adding it back into the array, without
> having to reboot?
Not really ... relying on a specific sdX name has been deprecated for a
while. To ensure absolute ordering, you should be using the device by
id or by label.
James
next prev parent reply other threads:[~2008-06-09 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 19:49 Reallocating sd device Richard Scobie
2008-06-09 19:54 ` James Bottomley [this message]
2008-06-09 20:17 ` Richard Scobie
2008-06-10 3:56 ` James Bottomley
2008-06-10 4:21 ` Richard Scobie
-- strict thread matches above, loose matches on Subject: below --
2008-06-09 0:17 Richard Scobie
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=1213041283.3508.66.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=richard@sauce.co.nz \
/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.