From: Brad Campbell <brad@wasp.net.au>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Janek Kozicki <janek_listy@wp.pl>,
linux-raid@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: mapping ataXX.YY to a /dev/sdX
Date: Sat, 10 Jul 2010 12:42:26 +0800 [thread overview]
Message-ID: <4C37FA32.8020008@wasp.net.au> (raw)
In-Reply-To: <alpine.DEB.1.10.1007082348190.23489@uplift.swm.pp.se>
On 09/07/10 05:53, Mikael Abrahamsson wrote:
> I never really had a huge problem figuring out with high probability
> which drive it was, but I wanted to know if there was a 100% certain way
> of doing it. Seems there is not, am I the only one who is looking for
> this functionality? I would think this is a fairly common problem?
Certainty would be nice, but in practice here I've always found that ataX = sdX+1 and I've relied on
that mapping to always be constant. I've not yet found it otherwise, but I guess it's possible. I'd
assume the libata guys should be able to provide a definite comment on that.
I've got no lights on my arrays, so it's even harder to identify which drive is which when you need
to swap one out live. I've resorted to keeping a log of which serial number is in which physical
slot, so I can look up the serial number of the failing drive with hdparm and I know I've got the
right one. Again, it still hinges on the ata-sd mapping being constant. (it also relies on me
updating the log when I swap a disk)
Brad
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
next prev parent reply other threads:[~2010-07-10 4:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 6:14 mapping ataXX.YY to a /dev/sdX Mikael Abrahamsson
2010-07-07 12:02 ` Daniel Pittman
2010-07-07 15:51 ` Mikael Abrahamsson
2010-07-08 10:05 ` Tim Small
2010-07-08 10:26 ` Mikael Abrahamsson
2010-07-08 10:44 ` Robin Hill
2010-07-08 11:05 ` Mikael Abrahamsson
2010-07-08 21:26 ` Janek Kozicki
2010-07-08 21:53 ` Mikael Abrahamsson
2010-07-10 4:42 ` Brad Campbell [this message]
2010-07-10 7:05 ` Rudy Zijlstra
2010-07-10 11:45 ` Anssi Hannula
2010-07-10 19:23 ` Jeff Garzik
2010-07-10 23:49 ` Rudy Zijlstra
2010-07-11 19:01 ` Jérôme Poulin
2010-07-14 19:05 ` Jim Paris
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=4C37FA32.8020008@wasp.net.au \
--to=brad@wasp.net.au \
--cc=janek_listy@wp.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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).