thr3ads.net - zfs discuss - [zfs-discuss] Disk IDs and DD [Aug 2011]

If this information is useful, please help other people find it:
Share via:

Lanky Doodle

2011-Aug-09 11:51 UTC

[zfs-discuss] Disk IDs and DD

Hiya,

Is there any reason (and anything to worry about) if disk target IDs
don''t start at 0 (zero). For some reason mine are like this (3
controllers - 1 onboard and 2 PCIe);

AVAILABLE DISK SELECTIONS:
       0. c8t0d0 <ATA    -ST9160314AS    -SDM1 cyl 19454 alt 2 hd 255 sec
63>
          /pci at 0,0/pci10de,cb84 at 5/disk at 0,0
       1. c8t1d0 <ATA    -ST9160314AS    -SDM1 cyl 19454 alt 2 hd 255 sec
63>
          /pci at 0,0/pci10de,cb84 at 5/disk at 1,0
       2. c9t7d0 <ATA-HitachiHDS72302-A5C0 cyl 60798 alt 2 hd 255 sec 252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at 7,0
       3. c9t8d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at 8,0
       4. c9t9d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at 9,0
       5. c9t10d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at a,0
       6. c9t11d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at b,0
       7. c9t12d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at c,0
       8. c9t13d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at d,0
       9. c9t14d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at e,0
      10. c10t8d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at 8,0
      11. c10t9d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at 9,0
      12. c10t10d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at a,0
      13. c10t11d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at b,0
      14. c10t12d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at c,0
      15. c10t13d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at d,0
      16. c10t14d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at e,0

So apart from the onboard controller, the tx (where x is the number)
doesn''t start at 0.

Also, I am trying to make disk LEDs blink by using dd so I can match up disks in
Solaris to the physical slot, but I can''t work out the right command;

admin at ok-server01:~# dd if=/dev/dsk/c9t7d0 of=/dev/null
dd: /dev/dsk/c9t7d0: open: No such file or directory

admin at ok-server01:~# dd if=/dev/rdsk/c9t7d0 of=/dev/null
dd: /dev/rdsk/c9t7d0: open: No such file or directory

Thanks
-- 
This message posted from opensolaris.org

LaoTsao

2011-Aug-09 14:54 UTC

head link

[zfs-discuss] Disk IDs and DD

nothing to worry about
as for dd you need s? in addition to c8t0d0

Sent from my iPad
Hung-Sheng Tsao ( LaoTsao) Ph.D

On Aug 9, 2011, at 4:51, Lanky Doodle <lanky_doodle at hotmail.com> wrote:
> Hiya,
> 
> Is there any reason (and anything to worry about) if disk target IDs
don''t start at 0 (zero). For some reason mine are like this (3
controllers - 1 onboard and 2 PCIe);
> 
> AVAILABLE DISK SELECTIONS:
>       0. c8t0d0 <ATA    -ST9160314AS    -SDM1 cyl 19454 alt 2 hd 255 sec
63>
>          /pci at 0,0/pci10de,cb84 at 5/disk at 0,0
>       1. c8t1d0 <ATA    -ST9160314AS    -SDM1 cyl 19454 alt 2 hd 255 sec
63>
>          /pci at 0,0/pci10de,cb84 at 5/disk at 1,0
>       2. c9t7d0 <ATA-HitachiHDS72302-A5C0 cyl 60798 alt 2 hd 255 sec
252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at 7,0
>       3. c9t8d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at 8,0
>       4. c9t9d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255 sec
252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at 9,0
>       5. c9t10d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at a,0
>       6. c9t11d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at b,0
>       7. c9t12d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at c,0
>       8. c9t13d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at d,0
>       9. c9t14d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at e,0
>      10. c10t8d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at 8,0
>      11. c10t9d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at 9,0
>      12. c10t10d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at a,0
>      13. c10t11d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at b,0
>      14. c10t12d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at c,0
>      15. c10t13d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at d,0
>      16. c10t14d0 <ATA    -Hitachi HDS7230-A5C0 cyl 60798 alt 2 hd 255
sec 252>
>          /pci at 0,0/pci10de,377 at f/pci1000,3140 at 0/sd at e,0
> 
> So apart from the onboard controller, the tx (where x is the number)
doesn''t start at 0.
> 
> Also, I am trying to make disk LEDs blink by using dd so I can match up
disks in Solaris to the physical slot, but I can''t work out the right
command;
> 
> admin at ok-server01:~# dd if=/dev/dsk/c9t7d0 of=/dev/null
> dd: /dev/dsk/c9t7d0: open: No such file or directory
> 
> admin at ok-server01:~# dd if=/dev/rdsk/c9t7d0 of=/dev/null
> dd: /dev/rdsk/c9t7d0: open: No such file or directory
> 
> Thanks
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Paul Kraus

2011-Aug-09 15:20 UTC

head link

[zfs-discuss] Disk IDs and DD

On Tue, Aug 9, 2011 at 7:51 AM, Lanky Doodle <lanky_doodle at hotmail.com>
wrote:
> Is there any reason (and anything to worry about) if disk target IDs
don''t start at 0
> (zero). For some reason mine are like this (3 controllers - 1 onboard and 2
PCIe);
>
> AVAILABLE DISK SELECTIONS:
> ? ? ? 0. c8t0d0 <ATA ? ?-ST9160314AS ? ?-SDM1 cyl 19454 alt 2 hd 255 sec
63>
> ? ? ? ? ?/pci at 0,0/pci10de,cb84 at 5/disk at 0,0
> ? ? ? 1. c8t1d0 <ATA ? ?-ST9160314AS ? ?-SDM1 cyl 19454 alt 2 hd 255 sec
63>
> ? ? ? ? ?/pci at 0,0/pci10de,cb84 at 5/disk at 1,0
> ? ? ? 2. c9t7d0 <ATA-HitachiHDS72302-A5C0 cyl 60798 alt 2 hd 255 sec
252>
> ? ? ? ? ?/pci at 0,0/pci10de,376 at a/pci1000,3140 at 0/sd at 7,0
    Nothing to worry about here. Controller IDs (c<n>) are assigned
based on the order the kernel probes the hardware. On the SPARC
systems you can usually change this in the firmware (OBP), but they
really don''t _mean_ anything (other than the kernel found c8 before it
found c9).

    There are (or were) other things the kernel considers a "disk
controller" on the system beyond the three you indicate. Keep in mind
that once the kernel finds a controller it makes an entry in
/etc/path_to_inst so that the IDs remain consistent if new controllers
are added (earlier in the search path).

-- 
{--------1---------2---------3---------4---------5---------6---------7---------}
Paul Kraus
-> Senior Systems Architect, Garnet River ( http://www.garnetriver.com/ )
-> Sound Designer: Frankenstein, A New Musical
(http://www.facebook.com/event.php?eid=123170297765140)
-> Sound Coordinator, Schenectady Light Opera Company (
http://www.sloctheater.org/ )
-> Technical Advisor, RPI Players

Brandon High

2011-Aug-09 18:05 UTC

head link

[zfs-discuss] Disk IDs and DD

On Tue, Aug 9, 2011 at 8:20 AM, Paul Kraus <paul at kraus-haus.org>
wrote:> ? ?Nothing to worry about here. Controller IDs (c<n>) are assigned
> based on the order the kernel probes the hardware. On the SPARC
> systems you can usually change this in the firmware (OBP), but they
> really don''t _mean_ anything (other than the kernel found c8
before it
> found c9).
If you''re really bothered by the device names, you can rebuild the
device map. There''s no reason to do it unless you''ve had to
replace
hardware, etc.

The steps are similar to these:
http://spiralbound.net/blog/2005/12/21/rebuilding-the-solaris-device-tree

-B

-- 
Brandon High : bhigh at freaks.com

Lanky Doodle

2011-Aug-10 07:56 UTC

head link

[zfs-discuss] Disk IDs and DD

Oh no I am not bothered at all about the target ID numbering. I just wondered if
there was a problem in the way it was enumerating the disks.

Can you elaborate on the dd command LaoTsao? Is the ''s'' you
refer to a parameter of the command or the slice of a disk - none of my
''data'' disks have been ''configured'' yet. I
wanted to ID them before adding them to pools.
-- 
This message posted from opensolaris.org

Andrew Gabriel

2011-Aug-10 08:04 UTC

head link

[zfs-discuss] Disk IDs and DD

Lanky Doodle wrote:> Oh no I am not bothered at all about the target ID numbering. I just
wondered if there was a problem in the way it was enumerating the disks.
>
> Can you elaborate on the dd command LaoTsao? Is the ''s''
you refer to a parameter of the command or the slice of a disk - none of my
''data'' disks have been ''configured'' yet. I
wanted to ID them before adding them to pools.
>   
Use p0 on x86 (whole disk, without regard to any partitioning).
Any other s or p device node may or may not be there, depending on what 
partitions/slices are on the disk.

-- 
Andrew Gabriel

Fajar A. Nugraha

2011-Aug-10 08:05 UTC

head link

[zfs-discuss] Disk IDs and DD

On Wed, Aug 10, 2011 at 2:56 PM, Lanky Doodle <lanky_doodle at
hotmail.com> wrote:> Can you elaborate on the dd command LaoTsao? Is the ''s''
you refer to a parameter of the command or the slice of a disk - none of my
''data'' disks have been ''configured'' yet. I
wanted to ID them before adding them to pools.
For starters, try looking at what files are inside /dev/dsk/. There
shouldn''t be a c9t7d0 file/symlink.

Next, Googling "solaris disk notation" found this entry:
http://multiboot.solaris-x86.org/iv/3.html. In short, for whole disk
you''d need /dev/dsk/c9t7d0p0

-- 
Fajar

Lanky Doodle

2011-Aug-10 12:33 UTC

head link

[zfs-discuss] Disk IDs and DD

Thanks Andrew, Fajar.
-- 
This message posted from opensolaris.org

Apparently Analagous Threads

Search for more seemingly similar threads

zfs discuss - Aug 2011 - Disk IDs and DD

[zfs-discuss] Disk IDs and DD

[zfs-discuss] Disk IDs and DD

[zfs-discuss] Disk IDs and DD

[zfs-discuss] Disk IDs and DD

[zfs-discuss] Disk IDs and DD

[zfs-discuss] Disk IDs and DD

[zfs-discuss] Disk IDs and DD

[zfs-discuss] Disk IDs and DD

Apparently Analagous Threads