LVM problem

[Igor Sovin]

Hi all !

I have the following problem:

I have server and disk storage. There are 3 LUNs on disk storage. In ioscan output on server I see 6 device files:
/dev/dsk/c16t0d0
/dev/dsk/c16t0d1
/dev/dsk/c16t0d1

/dev/dsk/c16t1d0
/dev/dsk/c16t2d0
/dev/dsk/c16t3d0

2 device files for each LUN, because there are two path to one LUN.
I'm vgimporting a volume group that exists on 3 LUNs

vgimport /dev/vg_sap /dev/dsk/c16t0d0 /dev/dsk/c16t0d1 /dev/dsk/c16t0d2

successfully

but I cant vgextend volume group with the last 3 disks (alternative paths).

The output of vgextend is :
# vgextend /dev/vg_sap /dev/dsk/c16t1d0
vgextend: Couldn't open physical volume "/dev/dsk/c16t1d0":
Invalid argument

What should I do to solve this problem?

[Trond Haugen]

Be sure you can access the disk thru the alternate path. Thiscan be tested with 'diskinfo /dev/rdsk/c16t1d0'.
My guess is that this will fail and you will need to check you HW. The fact that the dev-files are present means that the path probably worked at some point.

Regards,
Trond

[Igor Sovin]

Hi!
Yes you're right the "diskinfo" failed

#diskinfo /dev/rdsk/c16t1d0
SCSI describe of /dev/rdsk/c16t1d0:
vendor: HP
product id: A5277A
type: direct access
size: 0 Kbytes
bytes per sector: 0

:(

[Rgomes]

I guess, alternate paths of LUNs are not listed in /etc/lvmtab.

You have written, your primary paths are:

/dev/dsk/c16t0d0
/dev/dsk/c16t0d1------>same disk
/dev/dsk/c16t0d1------>same disk.

I guess, it's typo mistake. If not pls check with ioscan output again.

Have you tried with 'diskinfo' on primary and alternate disk?

If it is device related problem, then 'ioscan' and 'insf -e' can help you.

Regards,
Richard

[Elmar P. Kolkman]

I think the c16t[123]d0 devices are NOT your alternate paths. If they are, I don't see why you want this alternate path, since you still use the same controller for the primary and alternate path, leaving a SPOF...

Running ioscan and insf -e, as suggested above, should install device files if there is an alternate path not yet installed.

[Trond Haugen]

Well diskinfo isn't failing totally. It sees a device. But of zero size! So there sure is something wrong with this setup.
also I would have expected teh alternate dev-files to be:
/dev/dsk/c16t1d0
/dev/dsk/c16t1d1
/dev/dsk/c16t1d2

Do vgextend on the other dev-files fail in the same way?

Regards,
Trond

[Igor Sovin]

yes , /dev/dsk/c16t1d1 is typo mistake

disks are

c16t0d0
c16t0d1
c16t0d2

# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c0t0d0s2
/dev/vg_sap
/dev/dsk/c16t0d0
/dev/dsk/c16t0d1
/dev/dsk/c16t0d2

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 6 0/1/1/0.3.8.0.0.0.0 sdisk CLAIMED DEVICE HP A5277A
/dev/dsk/c16t0d0 /dev/rdsk/c16t0d0
disk 7 0/1/1/0.3.8.0.0.0.1 sdisk CLAIMED DEVICE HP A5277A
/dev/dsk/c16t0d1 /dev/rdsk/c16t0d1
disk 8 0/1/1/0.3.8.0.0.0.2 sdisk CLAIMED DEVICE HP A5277A
/dev/dsk/c16t0d2 /dev/insf26567 /dev/rdsk/c16t0d2
disk 9 0/1/1/0.3.8.0.0.1.0 sdisk CLAIMED DEVICE HP A5277A
/dev/dsk/c16t1d0 /dev/rdsk/c16t1d0
disk 10 0/1/1/0.3.8.0.0.2.0 sdisk CLAIMED DEVICE HP A5277A
/dev/dsk/c16t2d0 /dev/rdsk/c16t2d0
disk 11 0/1/1/0.3.8.0.0.3.0 sdisk CLAIMED DEVICE HP A5277A
/dev/dsk/c16t3d0 /dev/rdsk/c16t3d0
disk 12 0/1/1/0.3.8.0.0.3.7 sdisk CLAIMED DEVICE HP Universal Xport
/dev/dsk/c16t3d7 /dev/rdsk/c16t3d7
disk 2 0/1/2/0.2.21.255.0.0.0 sdisk CLAIMED DEVICE HP C1113M
/dev/dsk/c13t0d0 /dev/rdsk/c13t0d0
disk 3 0/1/2/0.2.21.255.0.0.1 sdisk CLAIMED DEVICE HP C1113M
/dev/dsk/c13t0d1 /dev/rdsk/c13t0d1
disk 4 0/1/2/0.2.21.255.0.0.2 sdisk CLAIMED DEVICE HP C1113M
/dev/dsk/c13t0d2 /dev/rdsk/c13t0d2
disk 5 0/1/2/0.2.21.255.0.0.3 sdisk CLAIMED DEVICE HP C1113M
/dev/dsk/c13t0d3 /dev/rdsk/c13t0d3


diskinfo on each of the 3 disks from /etc/lvmtab is successful

insf -e didnt help

[Rgomes]

Post vgdisplay -v vg_sap.

rgds
richard

[Elmar P. Kolkman]

To me it looks like you have only one path to each of your LUNS: c16t0d[012]
The other 3 devices are other LUNS, apparently empty ones. Check out your configuration of your disk array for this.

Also check out your devices. It looks like there is a really strange device: /dev/insf26567
I think you can savely remove it with rmsf

[Igor Sovin]

# vgdisplay -v vg_sap
--- Volume groups ---
VG Name /dev/vg_sap
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 21
Open LV 21
Max PV 16
Cur PV 3
Act PV 3
Max PE per PV 65535
VGDA 6
PE Size (Mbytes) 16
Total PE 19497
Alloc PE 16323
Free PE 3174
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg_sap/lvol1
LV Status available/syncd
LV Size (Mbytes) 1712
Current LE 107
Allocated PE 107
Used PV 2

LV Name /dev/vg_sap/lvol2
LV Status available/syncd
LV Size (Mbytes) 800
Current LE 50
Allocated PE 50
Used PV 1

LV Name /dev/vg_sap/lvol3
LV Status available/syncd
LV Size (Mbytes) 304
Current LE 19
Allocated PE 19
Used PV 1

LV Name /dev/vg_sap/lvol4
LV Status available/syncd
LV Size (Mbytes) 3008
Current LE 188
Allocated PE 188
Used PV 1

LV Name /dev/vg_sap/lvol5
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 32
Allocated PE 32
Used PV 1

LV Name /dev/vg_sap/lvol6
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 750
Allocated PE 750
Used PV 2

LV Name /dev/vg_sap/lvol7
LV Status available/syncd
LV Size (Mbytes) 22000
Current LE 1375
Allocated PE 1375
Used PV 3

LV Name /dev/vg_sap/lvol8
LV Status available/syncd
LV Size (Mbytes) 40960
Current LE 2560
Allocated PE 2560
Used PV 3

LV Name /dev/vg_sap/lvol9
LV Status available/syncd
LV Size (Mbytes) 55296
Current LE 3456
Allocated PE 3456
Used PV 3

LV Name /dev/vg_sap/lvol10
LV Status available/syncd
LV Size (Mbytes) 24000
Current LE 1500
Allocated PE 1500
Used PV 3

LV Name /dev/vg_sap/lvol11
LV Status available/syncd
LV Size (Mbytes) 18000
Current LE 1125
Allocated PE 1125
Used PV 3

LV Name /dev/vg_sap/lvol12
LV Status available/syncd
LV Size (Mbytes) 192
Current LE 12
Allocated PE 12
Used PV 2

LV Name /dev/vg_sap/lvol13
LV Status available/syncd
LV Size (Mbytes) 192
Current LE 12
Allocated PE 12
Used PV 2

LV Name /dev/vg_sap/lvol14
LV Status available/syncd
LV Size (Mbytes) 192
Current LE 12
Allocated PE 12
Used PV 2

LV Name /dev/vg_sap/lvol15
LV Status available/syncd
LV Size (Mbytes) 192
Current LE 12
Allocated PE 12
Used PV 2

LV Name /dev/vg_sap/lvol16
LV Status available/syncd
LV Size (Mbytes) 70000
Current LE 4375
Allocated PE 4375
Used PV 3

LV Name /dev/vg_sap/lvol17
LV Status available/syncd
LV Size (Mbytes) 112
Current LE 7
Allocated PE 7
Used PV 1

LV Name /dev/vg_sap/lvol18
LV Status available/syncd
LV Size (Mbytes) 3072
Current LE 192
Allocated PE 192
Used PV 2

LV Name /dev/vg_sap/lvol19
LV Status available/syncd
LV Size (Mbytes) 3504
Current LE 219
Allocated PE 219
Used PV 1

LV Name /dev/vg_sap/lvol36
LV Status available/syncd
LV Size (Mbytes) 112
Current LE 7
Allocated PE 7
Used PV 1

LV Name /dev/vg_sap/lvol37
LV Status available/syncd
LV Size (Mbytes) 5008
Current LE 313
Allocated PE 313
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c16t0d0
PV Status available
Total PE 5413
Free PE 0
Autoswitch On

PV Name /dev/dsk/c16t0d1
PV Status available
Total PE 5413
Free PE 1433
Autoswitch On

PV Name /dev/dsk/c16t0d2
PV Status available
Total PE 8671
Free PE 1741
Autoswitch On

[Fabio Ettore · Accepted solution]

Hi,

definitely the problem is the size of alternate path, it is zero! You should solve it before to vgextend the alternate path.

# vgextend /dev/vg_sap /dev/dsk/c16t2d0
# vgextend /dev/vg_sap /dev/dsk/c16t3d0

Do they fail with the same error?

Best regards,
Ettore

[Igor Sovin]

Hi!

Yes they fail with the same error

dont know what to do

[Igor Sovin]

How to solve problem with zero alternative path?

[Trond Haugen]

In my view the size being zero means that the dev-files are not "pointing" to the right devices. More of a HW than a SW problem. I would reccomend re-checking the cabeling. And remove the faulty dev-files and reboot.

Regards,
Trond