topic Re: 11.31 Disk layout corelations in Operating System - HP-UX

11.31 Disk layout corelations

Matthew Ghofrani — Fri, 27 Apr 2007 08:31:01 GMT

Is there a command in 11.31 to tell me which of my /dev/disk/disk## are corresponding to what shows up in ioscan such as /dev/dsk/c5t0d0?

Here is a quick out put that I need to correlate:

# ll ../disk
total 0
brw-r----- 1 bin sys 1 0x000001 Apr 24 12:41 disk51
brw-r----- 1 bin sys 1 0x000002 Apr 24 12:41 disk52
brw-r----- 1 bin sys 1 0x000003 Apr 24 12:41 disk53
brw-r----- 1 bin sys 1 0x000004 Apr 24 12:41 disk54
brw-r----- 1 bin sys 1 0x000005 Apr 24 12:41 disk55
brw-r----- 1 bin sys 1 0x000006 Apr 24 12:41 disk56
brw-r----- 1 bin sys 1 0x000007 Apr 24 12:41 disk57
brw-r----- 1 bin sys 1 0x000008 Apr 24 12:41 disk58
brw-r----- 1 bin sys 1 0x000009 Apr 24 12:41 disk59
brw-r----- 1 bin sys 1 0x00000a Apr 24 12:41 disk60
brw-r----- 1 bin sys 1 0x00000b Apr 24 12:41 disk61
brw-r----- 1 bin sys 1 0x00000c Apr 24 12:41 disk62
brw-r----- 1 bin sys 1 0x00000d Apr 24 12:41 disk63
brw-r----- 1 bin sys 1 0x00000e Apr 24 12:41 disk64
brw-r----- 1 bin sys 1 0x000010 Apr 24 12:41 disk65

/dev/dsk/c7t0d0 /dev/rdsk/c7t0d0
/dev/dsk/c7t0d1 /dev/rdsk/c7t0d1
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
/dev/dsk/c5t0d1 /dev/rdsk/c5t0d1
/dev/dsk/c11t0d0 /dev/rdsk/c11t0d0
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1

Re: 11.31 Disk layout corelations

Don Morris_1 — Fri, 27 Apr 2007 08:54:06 GMT

This close enough? (I think rdisk and disk correlate.. but I'm a memory guy, not disk - so take this with a grain of salt...):

# ioscan -k -m dsf
Persistent DSF Legacy DSF(s)
========================================
/dev/pt/pt1 /dev/rscsi/c2t7d0
/dev/rdisk/disk18 /dev/rdsk/c2t4d0
/dev/rdisk/disk19 /dev/rdsk/c2t5d0
/dev/rdisk/disk20 /dev/rdsk/c2t3d0
/dev/rdisk/disk21 /dev/rdsk/c2t2d0
/dev/rdisk/disk22 /dev/rdsk/c2t1d0
/dev/rdisk/disk23 /dev/rdsk/c2t0d0
/dev/rdisk/disk24 /dev/rdsk/c2t8d0
/dev/rdisk/disk25 /dev/rdsk/c2t14d0
/dev/rdisk/disk26 /dev/rdsk/c2t13d0
/dev/rdisk/disk27 /dev/rdsk/c2t12d0
/dev/rdisk/disk28 /dev/rdsk/c2t11d0
/dev/rdisk/disk29 /dev/rdsk/c2t10d0
/dev/rdisk/disk30 /dev/rdsk/c2t9d0
/dev/rdisk/disk31 /dev/rdsk/c0t6d0
/dev/rdisk/disk31_p1 /dev/rdsk/c0t6d0s1
/dev/rdisk/disk31_p2 /dev/rdsk/c0t6d0s2
/dev/rdisk/disk31_p3 /dev/rdsk/c0t6d0s3
/dev/rdisk/disk32 /dev/rdsk/c0t5d0

Re: 11.31 Disk layout corelations

Duncan Edmonstone — Fri, 27 Apr 2007 08:54:29 GMT

# ioscan -m dsf /dev/disk/disk5

Persistent DSF Legacy DSF(s)
========================================
/dev/disk/disk5 /dev/dsk/c2t1d0
/dev/dsk/c3t1d0

HTH

Duncan

Re: 11.31 Disk layout corelations

James R. Ferguson — Fri, 27 Apr 2007 08:54:38 GMT

Hi:

No, no differently than in previous releases as long a you remain with the legacy LVM nomenclature for devices.

_However_ a new Agile Naming model available in 11.31 can help:

http://docs.hp.com/en/LVMmigration1/LVM_Migration_to_Agile.pdf

Regards!

...JRF...

Re: 11.31 Disk layout corelations

Matthew Ghofrani — Fri, 27 Apr 2007 11:37:44 GMT

Thank you all. That special ioscan was the answer I was looking for.

Re: 11.31 Disk layout corelations

Torsten. — Fri, 27 Apr 2007 12:00:50 GMT

I would prefer to use the new device files, like

/dev/disk/disk5

for any operation to prevent problems (seen in some threads here already).

As mentioned,

ioscan -m dsf

Re: 11.31 Disk layout corelations

Matthew Ghofrani — Fri, 27 Apr 2007 13:32:56 GMT

So in that case are you going to use /dev/rdisk/disk# for pvcreate and use /dev/disk/disk# for vgcreate?

Re: 11.31 Disk layout corelations

Torsten. — Fri, 27 Apr 2007 13:45:21 GMT

Yes, it just looks not nice to see both,

/dev/dsk/cxtydy and
/dev/disk/diskx

in any vgdisplay and other LVM related commands.

I don't know about the influence of using the "old" dev files, but there is some, see also

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1121849

Re: 11.31 Disk layout corelations

Matthew Ghofrani — Tue, 01 May 2007 08:24:00 GMT

So here is what I did, and the error that I get.(I took out some of the outputs)

# insf -eCdisk
insf: Installing special files for sdisk instance 48 address 2/0/0/2/0.6.0
insf: Installing special files for sdisk instance 50 address 2/0/0/2/1.2.0
insf: Installing special files for sdisk instance 49 address 2/0/0/3/0.6.0
insf: Installing special files for sdisk instance 12 address 2/0/8/1/0.1.4.239.0.0.0
insf: Installing special files for sdisk instance 35 address 2/0/10/1/0.1.5.239.0.1.3
insf: Installing special files for esdisk instance 51 address 64000/0xfa00/0x1
insf: Installing special files for esdisk instance 52 address 64000/0xfa00/0x2

root@monroe [/root]
# ioscan -m dsf
Persistent DSF Legacy DSF(s)
========================================
/dev/rtape/tape1_BEST /dev/rmt/c3t6d0BEST
/dev/rtape/tape1_BESTn /dev/rmt/c3t6d0BESTn
/dev/rtape/tape1_BESTb /dev/rmt/c3t6d0BESTb
/dev/rtape/tape1_BESTnb /dev/rmt/c3t6d0BESTnb
/dev/pt/pt4 /dev/rscsi/c6t15d0
/dev/rscsi/c4t15d0
/dev/rscsi/c10t15d0
/dev/rscsi/c8t15d0
/dev/rdisk/disk51 /dev/rdsk/c5t0d0
/dev/rdsk/c7t0d0
/dev/rdsk/c11t0d0
/dev/rdsk/c9t0d0
/dev/rdisk/disk52 /dev/rdsk/c5t0d1
/dev/rdsk/c7t0d1
/dev/rdsk/c11t0d1
/dev/rdsk/c9t0d1
/dev/rdisk/disk62 /dev/rdsk/c5t1d3
/dev/rdsk/c7t1d3
/dev/rdsk/c9t1d3
/dev/rdsk/c11t1d3
/dev/rdisk/disk63 /dev/rdsk/c0t6d0
/dev/rdisk/disk64 /dev/rdsk/c2t6d0
/dev/rdisk/disk65 /dev/rdsk/c1t2d0

root@monroe [/root]
# pvcreate -f /dev/rdisk/disk51
Physical volume "/dev/rdisk/disk51" has been successfully created.

root@monroe [/root]
# ll /dev/vg01
total 0
crw-r--r-- 1 root sys 64 0x010000 Apr 26 12:55 group

root@monroe [/root]
# vgcreate /dev/vg01 /dev/disk/disk51
Increased the number of physical extents per physical volume to 2559.
vgcreate: Volume group "/dev/vg01" could not be created:
Unable to read the physical volume.

Re: 11.31 Disk layout corelations

Torsten. — Tue, 01 May 2007 08:42:32 GMT

What kind of storage device is it?

Re: 11.31 Disk layout corelations

Matthew Ghofrani — Tue, 01 May 2007 09:06:25 GMT

They are clarrion. Should also say that this is a cold start of 11.31 and the vg00 shows the correct dsf disks.
# strings /etc/lvmtab
/dev/vg00
eF.2
/dev/disk/disk63

If you think this is storage or driver's firmware related, I'll chase it that way

Re: 11.31 Disk layout corelations

Matthew Ghofrani — Tue, 01 May 2007 09:42:55 GMT

Also, here is the scsimgr output to disk51;
LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk51

Total number of LUN paths = 4
World Wide Identifier(WWID) = 0x60060160b2cf1900d87f1979dcf1db11

LUN path : lunpath2
Class = lunpath
Instance = 2
Hardware path = 2/0/8/1/0.0x5006016139a01dad.0x4000000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath3
Class = lunpath
Instance = 3
Hardware path = 2/0/8/1/0.0x5006016939a01dad.0x4000000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath28
Class = lunpath
Instance = 28
Hardware path = 2/0/10/1/0.0x5006016b39a01dad.0x4000000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath31
Class = lunpath
Instance = 31
Hardware path = 2/0/10/1/0.0x5006016339a01dad.0x4000000000000000
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

Re: 11.31 Disk layout corelations

Geoff Wild — Tue, 01 May 2007 14:53:29 GMT

Can you do a diskinfo /dev/rdisk/disk51

I recently added a disk to my workstation - looking at my history, I did this:

ioscan -m dsf
pvcreate /dev/rdisk/disk6
ioscan -m dsf
ioscan -fnC disk
insf -eC disk
ioscan -fnC disk
ioscan -m dsf
diskinfo /dev/rdisk/disk6
mkdir /dev/vg20
mknod /dev/vg20/group c 64 0x140000
ioscan -m dsf
vgcreate -s 32 -p 64 -e 32768 /dev/vg20 /dev/disk/disk6

Rgds...Geoff

Re: 11.31 Disk layout corelations

Matthew Ghofrani — Tue, 01 May 2007 15:47:11 GMT

Hereis the diskinfo..and I pretty much did what you had done, but will do it in that order one more time:
# diskinfo /dev/rdisk/disk51
SCSI describe of /dev/rdisk/disk51:
vendor: DGC
product id: CX3-80WDR5
type: direct access
size: 10485760 Kbytes
bytes per sector: 512