linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <Paul.Clements@SteelEye.com>
To: "Deas, Jim" <James.Deas@warnerbros.com>
Cc: Linux RAID Mailing Liste <linux-raid@vger.kernel.org>
Subject: Re: 3ware and scsi ids
Date: Tue, 10 Jun 2003 12:21:12 -0400	[thread overview]
Message-ID: <3EE60578.15B28E20@SteelEye.com> (raw)
In-Reply-To: 12F8DBE91382164-01@MMS__ad.corp.aoltw.net_

"Deas, Jim" wrote:
> 
> Have you tried this on the 3ware product? They do not
> return scsi data as a normal drive would. As far as I
> can tell, without making a 3ware specific system call
> you can not get a unique serial number from the drives.

The UUID referenced below is gotten from the md device superblock (data
written to the end of the disk) so there shouldn't be any issues with
devices that do not return a valid SCSI serial number or device ID.

--
Paul 


 
> -----Original Message-----
> From: Friedrich Lobenstock [mailto:fl@fl.priv.at]
> Sent: Friday, June 06, 2003 4:51 PM
> To: Linux RAID Mailing Liste
> Cc: linux-scsi@vger.kernel.org
> Subject: Re: 3ware and scsi ids
> 
> Deas, Jim wrote:
> > I am currently using 3wares products to create 2T raids.
> > To increase performance on my NAS type boxes I am
> > using software raids.
> >  My problem relates to a falure of a IDE drive.
> > Once a drive fails the next boot of the machine remaps all scsi ids.
> > so /dev/sda-adi becomes /dev/sda-sdh.
> > In short, if /dev/sdb dies, all raids become bad as all scsi ids
> > shift down making my raidtab file now point at the wrong drives.
> > (I assume this will also be a possible problem when I use
> > my USB dongle to update software.)
> >
> >  Is there a way to hard assign logical /dev/sd(x) in the driver
> > so they will always map the same ide port on the 3ware controllers?
> > 3ware is no help on this. They say it is the bios/system and they
> > have no control over this.
> 
> You'd better use mdadm instead of the raidtools.
> 
> The config file for mdadm looks like this:
> # cat /etc/mdadm.conf
> DEVICE /dev/hd* /dev/sd*
> ARRAY /dev/md0 level=raid1 num-devices=2 UUID=52094036:b2e9cf8b:4267c923:750757da
> 
> So you do not have to worry about which drive gets assigned which
> scsi id.
> 
> A
>     /sbin/mdadm --assemble --scan
> will do the trick.
> 
> Get it at http://www.cse.unsw.edu.au/~neilb/source/mdadm/
> 
> --
> MfG / Regards
> Friedrich Lobenstock
> ____________________________________________________________________
> Friedrich Lobenstock                       Linux Services Lobenstock
> URL: http://www.lsl.at/                         Email: fl@fl.priv.at
> ____________________________________________________________________
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2003-06-10 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10 16:16 3ware and scsi ids Deas, Jim
2003-06-10 16:21 ` Paul Clements [this message]
     [not found] <12C23B584849261-01@MMS__ad.corp.aoltw.net_>
2003-06-06 23:51 ` Friedrich Lobenstock

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=3EE60578.15B28E20@SteelEye.com \
    --to=paul.clements@steeleye.com \
    --cc=James.Deas@warnerbros.com \
    --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).