Smit, Disk ordering is not done by mpt2sas driver. Ordering is purely depend upon How FW discovers drivers and repots it to Driver. e.a if you have slow spinning driver at slot-0, it can be reported by FW at the end, though it is attached to slot-0. In summary, Disk ordering is not guaranteed. ~ Kashyap > -----Original Message----- > From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi- > owner@xxxxxxxxxxxxxxx] On Behalf Of Caspar Smit > Sent: Friday, May 13, 2011 4:04 PM > To: linux-scsi@xxxxxxxxxxxxxxx > Subject: Re: mpt2sas: bug in disk ordering? > > Hello again, > > I tried with Debian Squeeze with the latest backports kernel 2.6.38, > which has mpt2sas version 07.100.00.00 > and now the disks are ordered this way: > > /dev/sdb = slot 3 > /dev/sdc = slot 2 > /dev/sdd = slot 1 > /dev/sde = slot 0 > /dev/sdf = slot 7 > /dev/sdg = slot 6 > /dev/sdh = slot 5 > /dev/sdi = slot 4 > > So there's more consistency here but still ordered backwards (per port) > > Kind regards, > > Caspar Smit > > > 2011/5/13 Caspar Smit <c.smit@xxxxxxxxxx>: > > Hi all, > > > > I'm having a minor issue with the disk ordering using an LSI 9211-8i > > (mpt2sas) controller. > > > > If i go into the controllers SAS config utility during boot I can > > identify the disks in the slots. > > > > disk 0 -> slot 0, disk 1 -> slot 1, etc.. everyhting is fine. > > > > When I boot into debian linux lenny (using the latest backports > > 2.6.32-31 kernel, this kernel has version 02.100.03.00 of the mpt2sas > > driver) > > > > The disks are ordered this way: > > > > /dev/sda = internal SSD connected to the MB > > > > /dev/sdb = slot 0 > > /dev/sdc = slot 1 > > /dev/sdd = slot 2 > > /dev/sde = slot 3 > > /dev/sdf = slot 7 (!) > > /dev/sdg = slot 4 > > /dev/sdh = slot 5 > > /dev/sdi = slot 6 > > > > So it seems the first 4 disks connected to SAS port 1 are ordered > > correctly and the last 4 disks are not. > > > > When I check /dev/disk/by-path i see the following: > > > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 pci-0000:04:00.0-sas- > > 0x500605b001d161b0:1:0-0x4433221103000000:0 -> ../../sdb > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 > > pci-0000:04:00.0-sas-0x500605b001d161b0:1:1-0x4433221102000000:0 -> > > ../../sdc > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 > > pci-0000:04:00.0-sas-0x500605b001d161b0:1:2-0x4433221101000000:0 -> > > ../../sdd > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 > > pci-0000:04:00.0-sas-0x500605b001d161b0:1:3-0x4433221100000000:0 -> > > ../../sde > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 > > pci-0000:04:00.0-sas-0x500605b001d161b0:1:4-0x4433221104000000:0 -> > > ../../sdf > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 > > pci-0000:04:00.0-sas-0x500605b001d161b0:1:5-0x4433221107000000:0 -> > > ../../sdg > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 > > pci-0000:04:00.0-sas-0x500605b001d161b0:1:6-0x4433221106000000:0 -> > > ../../sdh > > lrwxrwxrwx 1 root root 9 2011-05-13 10:52 > > pci-0000:04:00.0-sas-0x500605b001d161b0:1:7-0x4433221105000000:0 -> > > ../../sdi > > > > This LOOKS as it should but right now it is not really correct > because > > 1:7 indicates that it should be physical slot 7 (sdi is in slot 6 and > > not in slot 7) > > > > When i use the sas2ircu command line util to LOCATE the disks and I > > use 1:7 to locate, slot 7 lights up (NOT disk sdi) > > > > Is this behavior fixed in a newer version of the driver, and if so > > what is the corresponding patch to fix this? > > > > Kind regards, > > > > Caspar Smit > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-scsi" > in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
