On 02/28/11 22:39, Dave Pooser wrote:
On 2/28/11 4:23 PM, Garrett D'Amore garr...@nexenta.com
wrote:
Drives are ordered in the order they are *enumerated* when they
*first*
show up in the system. *Ever*.
Is the same true of controllers? That is, will c12 remain c12 or
Date: Mon, 28 Feb 2011 22:02:37 +0100 (CET)
From: Roy Sigurd Karlsbakk r...@karlsbakk.net
I cannot but agree. On Linux and Windoze (haven't tested FreeBSD),
drives connected to an LSI9211 show up in the correct order, but
not
on OI/osol/S11ex (IIRC), and fmtopo doesn't always show a
Last I checked, it didn't help much. IMHO we need a driver that can
display the drives in the order they're plugged in. Like Windoze.
Like Linux. Like FreeBSD. I really don't understand what should be
so hard to do it like the others. As one said I don't have their
sources, both Linux
On Thu, 2011-03-03 at 21:02 +0100, Roy Sigurd Karlsbakk wrote:
Last I checked, it didn't help much. IMHO we need a driver that can
display the drives in the order they're plugged in. Like Windoze.
Like Linux. Like FreeBSD. I really don't understand what should be
so hard to do it like
(Dave P...I sent this yesterday, but it bounced on your email address)
A small comment from me would be to create some test pools and replace
devices in the pools to see if device names remain the same or change
during these operations.
If the device names change and the pools are unhappy,
Surprised that one of the most approachable outputs for any customer to
use which would enable simple identification/resolution of many
of these discussions didn't come up, namely:
cfgadm -al
for a reasonable physical mapping in which SAS/SATA drives are
relatively easy to map out by ID
On 2/27/11 11:13 PM, James C. McPherson j...@opensolaris.org wrote:
/pci@0,0/pci8086,340c@5/pci1000,3020@0
and
/pci@0,0/pci8086,340e@7/pci1000,3020@0
which are in different slots on your motherboard and connected to
different PCI Express Root Ports - which should help with transfer
rates amongst
I cannot but agree. On Linux and Windoze (haven't tested FreeBSD),
drives connected to an LSI9211 show up in the correct order, but not
on OI/osol/S11ex (IIRC), and fmtopo doesn't always show a mapping
between device name and slot, since that relies on the SES hardware
being properly
On 1/03/11 03:00 AM, Dave Pooser wrote:
On 2/27/11 11:13 PM, James C. McPhersonj...@opensolaris.org wrote:
/pci@0,0/pci8086,340c@5/pci1000,3020@0
and
/pci@0,0/pci8086,340e@7/pci1000,3020@0
which are in different slots on your motherboard and connected to
different PCI Express Root Ports -
On 1/03/11 07:02 AM, Roy Sigurd Karlsbakk wrote:
...
Last I checked, it didn't help much. IMHO we need a driver that can
display the drives in the order they're plugged in. Like Windoze.
Like Linux. Like FreeBSD. I really don't understand what should be
so hard to do it like the others. As
On 2/28/11 4:23 PM, Garrett D'Amore garr...@nexenta.com wrote:
Drives are ordered in the order they are *enumerated* when they *first*
show up in the system. *Ever*.
Is the same true of controllers? That is, will c12 remain c12 or
/pci@0,0/pci8086,340c@5 remain /pci@0,0/pci8086,340c@5 even if
On 27/02/11 05:24 PM, Dave Pooser wrote:
On 2/26/11 7:43 PM, Bill Sommerfeldsommerf...@hamachi.org wrote:
On your system, c12 is the mpxio virtual controller; any disk which is
potentially multipath-able (and that includes the SAS drives) will
appear as a child of the virtual controller
On 2/27/11 5:15 AM, James C. McPherson j...@opensolaris.org wrote:
On 27/02/11 05:24 PM, Dave Pooser wrote:
On 2/26/11 7:43 PM, Bill Sommerfeldsommerf...@hamachi.org wrote:
On your system, c12 is the mpxio virtual controller; any disk which is
potentially multipath-able (and that includes the
I can live with that-- but I really want to know what (real, not virtual)
controllers disks are connected to; I want to build 3 8-disk RAIDz2 vdevs
now (with room for a fourth for expansion later) and I really want to make
sure each of those vdevs has fewer than three disks per controller so
On 2/27/11 11:18 AM, Roy Sigurd Karlsbakk r...@karlsbakk.net wrote:
I cannot but agree. On Linux and Windoze (haven't tested FreeBSD), drives
connected to an LSI9211 show up in the correct order, but not on
OI/osol/S11ex (IIRC), and fmtopo doesn't always show a mapping between
device name and
On 28/02/11 07:30 AM, Dave Pooser wrote:
On 2/27/11 11:18 AM, Roy Sigurd Karlsbakkr...@karlsbakk.net wrote:
I cannot but agree. On Linux and Windoze (haven't tested FreeBSD), drives
connected to an LSI9211 show up in the correct order, but not on
OI/osol/S11ex (IIRC), and fmtopo doesn't
On 28/02/11 03:18 AM, Roy Sigurd Karlsbakk wrote:
I can live with that-- but I really want to know what (real, not
virtual) controllers disks are connected to; I want to build 3 8-disk
RAIDz2 vdevs now (with room for a fourth for expansion later) and I
really want to make sure each of those
On 28/02/11 02:08 AM, Dave Pooser wrote:
On 2/27/11 5:15 AM, James C. McPhersonj...@opensolaris.org wrote:
On 27/02/11 05:24 PM, Dave Pooser wrote:
On 2/26/11 7:43 PM, Bill Sommerfeldsommerf...@hamachi.org wrote:
On your system, c12 is the mpxio virtual controller; any disk which is
On 2/27/11 4:07 PM, James C. McPherson j...@opensolaris.org wrote:
I misread your initial email, sorry.
No worries-- I probably could have written it more clearly.
So your disks are connected to separate PHYs on the HBA, by virtue
of their cabling. You can see this for yourself by looking at
On 28/02/11 12:46 PM, Dave Pooser wrote:
On 2/27/11 4:07 PM, James C. McPhersonj...@opensolaris.org wrote:
...
PHY iport@
01
12
24
38
410
520
640
780
OK, bear with me for a moment because I'm feeling extra dense this evening.
The PHY tells me which port on
On 2/27/11 10:06 PM, James C. McPherson j...@opensolaris.org wrote:
I've arranged these by devinfo path:
1st controller
c10t2d0
/pci@0,0/pci8086,340a@3/pci1000,72@0/iport@4/disk@p2,0
c15t5000CCA222E006B6d0
/pci@0,0/pci8086,340a@3/pci1000,72@0/iport@8/disk@w5000cca222e006b6,0
On 28/02/11 02:51 PM, Dave Pooser wrote:
On 2/27/11 10:06 PM, James C. McPhersonj...@opensolaris.org wrote:
...
2nd controller
c16t5000CCA222DDD7BAd0
/pci@0,0/pci8086,340c@5/pci1000,3020@0/iport@2/disk@w5000cca222ddd7ba,0
3rd controller
c14t5000CCA222DF8FBEd0
On Feb 27, 2011, at 9:18 AM, Roy Sigurd Karlsbakk wrote:
I can live with that-- but I really want to know what (real, not virtual)
controllers disks are connected to; I want to build 3 8-disk RAIDz2 vdevs
now (with room for a fourth for expansion later) and I really want to make
sure each of
The hardware: SuperMicro 847A chassis (3 drive bays in 4U) -- A means
there are 9 SFF-8087 ports on the backplanes, each controlling 4 drives;
no expanders here.
SuperMicro X8DTH-6F motherboard with integrated LSI 2008 SAS chipset,
flashed to IT firmware, connected to one backplane port.
Four LSI
On 02/26/11 17:21, Dave Pooser wrote:
While trying to add drives one at a time so I can identify them for later
use, I noticed two interesting things: the controller information is
unlike any I've seen before, and out of nine disks added after the boot
drive all nine are attached to c12 -- and
On 2/26/11 7:43 PM, Bill Sommerfeld sommerf...@hamachi.org wrote:
On your system, c12 is the mpxio virtual controller; any disk which is
potentially multipath-able (and that includes the SAS drives) will
appear as a child of the virtual controller (rather than appear as the
child of two or more
26 matches
Mail list logo
