linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Peter W. Morreale" <morreale@sgi.com>
To: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: some general md raid questions
Date: Wed, 12 Oct 2011 13:33:34 -0600	[thread overview]
Message-ID: <1318448014.6598.76.camel@hermosa.site> (raw)
In-Reply-To: <ps0hm8xas5.ln2@goaway.wombat.san-francisco.ca.us>

On Wed, 2011-10-12 at 10:55 -0700, Keith Keller wrote: 
> On 2011-10-12, Peter W. Morreale <morreale@sgi.com> wrote:
> >
> > Assuming I have two or more jbods attached to the machine, how can I
> > determine which disks are associated with which paths?  (Yes, sorry, I
> > realize this is a general discovery question and not specific to
> > raid :-)
> 
> Not positive this is what you want, but you can look at the udevinfo
> tool:

DOH!  Of course, I can look at the PCI addressing. 

Thanks,
-PWM


> 
> # udevinfo -q all -n sdc1
> P: /block/sdc/sdc1
> N: sdc1
> S: disk/by-id/scsi-1AMCC_A367495389E5F400123E-part1
> S: disk/by-path/pci-0000:01:03.0-scsi-0:0:1:0-part1
> E: ID_VENDOR=AMCC
> E: ID_MODEL=9550SX-16M_DISK
> E: ID_REVISION=3.02
> E: ID_SERIAL=1AMCC_A367495389E5F400123E
> E: ID_TYPE=disk
> E: ID_BUS=scsi
> E: ID_PATH=pci-0000:01:03.0-scsi-0:0:1:0
> 
> I hope someone else can answer your other questions; I've just started
> using mdraid myself.  I have played with the speed_limit parameters, but
> haven't noticed a huge difference (likely because they aren't good
> disks, not a fault with md).
> 
> --keith
> 



      reply	other threads:[~2011-10-12 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 14:47 some general md raid questions Peter W. Morreale
2011-10-12 17:55 ` Keith Keller
2011-10-12 19:33   ` Peter W. Morreale [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=1318448014.6598.76.camel@hermosa.site \
    --to=morreale@sgi.com \
    --cc=kkeller-usenet@wombat.san-francisco.ca.us \
    --cc=linux-raid@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).