Re: SAS scsibus target numbering

2012-07-27 Thread Brett Lymn
On Fri, Jul 27, 2012 at 09:49:38AM +1000, Simon Burge wrote: > > > > ISTR SPARC machines used an initiator address 6 for hysterical reasons. I > > forget why. > > Likewise for some early models of DECstation (2100 and 3100?). I never > understood why. > Priorities. When negotiating for the

Re: SAS scsibus target numbering

2012-07-26 Thread Matt Thomas
On Jul 26, 2012, at 9:07 PM, Alistair Crooks wrote: > On Fri, Jul 27, 2012 at 07:35:19AM +1000, matthew green wrote: >> >>> I have a (mpt) SAS with seven discs connected. >>> The discs attach as sd0..sd6, but the SCSI target numbers are 0..5 and 7. >>> It appears to me that someone is skippig ID

Re: SAS scsibus target numbering

2012-07-26 Thread Alistair Crooks
On Fri, Jul 27, 2012 at 07:35:19AM +1000, matthew green wrote: > > > I have a (mpt) SAS with seven discs connected. > > The discs attach as sd0..sd6, but the SCSI target numbers are 0..5 and 7. > > It appears to me that someone is skippig ID 6 for the controller. > > It doesn't hurt too much, but

re: SAS scsibus target numbering

2012-07-26 Thread matthew green
> > it's usual for the SCSI HBA to assign a targetID for itself. > > For real SCSI - ie, non-SAS - it's actually necessary; the protocols > used for initiators and targets to speak with one another require a > line for the initiator as well as for the target. But the host is > usually ID 7. > >

Re: SAS scsibus target numbering

2012-07-26 Thread Simon Burge
Eduardo Horvath wrote: > On Thu, 26 Jul 2012, Mouse wrote: > > > > it's usual for the SCSI HBA to assign a targetID for itself. > > > > For real SCSI - ie, non-SAS - it's actually necessary; the protocols > > used for initiators and targets to speak with one another require a > > line for the in

Re: SAS scsibus target numbering

2012-07-26 Thread Mouse
>>> it's usual for the SCSI HBA to assign a targetID for itself. >> For real SCSI - ie, non-SAS - it's actually necessary; [...]. But >> the host is usually ID 7. > ISTR SPARC machines used an initiator address 6 for hysterical > reasons. I forget why. That disagrees with my experience. The SPA

Re: SAS scsibus target numbering

2012-07-26 Thread Eduardo Horvath
On Thu, 26 Jul 2012, Mouse wrote: > > it's usual for the SCSI HBA to assign a targetID for itself. > > For real SCSI - ie, non-SAS - it's actually necessary; the protocols > used for initiators and targets to speak with one another require a > line for the initiator as well as for the target. Bu

Re: SAS scsibus target numbering

2012-07-26 Thread Edgar Fuß
> besides having to use a different number, is there any real reason > you want to change them? Just trying to avoid confusion. I now have already have five different numbering scemes: ID2=sd2=dk0=component0=column 1. Fortunately two of then coincide and so I have three of them only differing by a

Re: SAS scsibus target numbering

2012-07-26 Thread Mouse
> it's usual for the SCSI HBA to assign a targetID for itself. For real SCSI - ie, non-SAS - it's actually necessary; the protocols used for initiators and targets to speak with one another require a line for the initiator as well as for the target. But the host is usually ID 7. Perhaps this is

re: SAS scsibus target numbering

2012-07-26 Thread matthew green
> I have a (mpt) SAS with seven discs connected. > The discs attach as sd0..sd6, but the SCSI target numbers are 0..5 and 7. > It appears to me that someone is skippig ID 6 for the controller. > It doesn't hurt too much, but it took me a while to find out why detaching > targets 2, 3, 4 and 5 wor

Re: SAS scsibus target numbering

2012-07-26 Thread Eduardo Horvath
On Thu, 26 Jul 2012, Edgar Fu? wrote: > > You can change them arbitrarily by messing with mpt > > either from BIOS or their command line utilities. > I tried the BIOS configuration (the one you get by typing Ctrl-C > at the right time, but I couldn't anything to assign target IDs. > Do you rememb

Re: SAS scsibus target numbering

2012-07-26 Thread Edgar Fuß
> "target IDs" are assigned by the mpt firmware. I suspected that. > You can change them arbitrarily by messing with mpt > either from BIOS or their command line utilities. I tried the BIOS configuration (the one you get by typing Ctrl-C at the right time, but I couldn't anything to assign target

Re: SAS scsibus target numbering

2012-07-26 Thread Edgar Fuß
I don't understand. I wrote: > The discs attach as sd0..sd6, so nailing down the autoconfig wouldn't change anything. What I would like to change are the SCSI target numbers. I wrote: > but the SCSI target numbers are 0..5 and 7. but I would like those targets to be 0..6. So it looks like the mp

Re: SAS scsibus target numbering

2012-07-26 Thread Eduardo Horvath
On Thu, 26 Jul 2012, Edgar Fu? wrote: > I have a (mpt) SAS with seven discs connected. > The discs attach as sd0..sd6, but the SCSI target numbers are 0..5 and 7. > It appears to me that someone is skippig ID 6 for the controller. > It doesn't hurt too much, but it took me a while to find out why

Re: SAS scsibus target numbering

2012-07-26 Thread Thor Lancelot Simon
On Thu, Jul 26, 2012 at 02:33:15PM +0200, Edgar Fu? wrote: > I have a (mpt) SAS with seven discs connected. > The discs attach as sd0..sd6, but the SCSI target numbers are 0..5 and 7. > It appears to me that someone is skippig ID 6 for the controller. > It doesn't hurt too much, but it took me a wh

SAS scsibus target numbering

2012-07-26 Thread Edgar Fuß
I have a (mpt) SAS with seven discs connected. The discs attach as sd0..sd6, but the SCSI target numbers are 0..5 and 7. It appears to me that someone is skippig ID 6 for the controller. It doesn't hurt too much, but it took me a while to find out why detaching targets 2, 3, 4 and 5 worked and 6 d