1833897 Members
1785 Online
110063 Solutions
New Discussion

extending a VG

 
Feljav
Frequent Advisor

extending a VG

I am trying to extend a /dev/vg02 and I received a error message. When I wrote pvdisplay of the disk that belong to vg02, this is the output:
**********************************************
pvdisplay /dev/dsk/c12t0d2
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c14t0d2":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query all of the physical volumes.
--- Physical volumes ---
PV Name /dev/dsk/c12t0d2
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c14t0d2":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query all of the physical volumes.
VG Name /dev/vg02
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 4
Total PE 17149
Free PE 899
Allocated PE 16250
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

The vgdisplay of vg02 is:

*****************************
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c14t0d2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg02
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 17152
VGDA 2
PE Size (Mbytes) 4
Total PE 17149
Alloc PE 16250
Free PE 899
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c14t0d2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg02/lvol2
LV Status available/syncd
LV Size (Mbytes) 65000
Current LE 16250
Allocated PE 16250
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c12t0d2
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c14t0d2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 17149
Free PE 899
Autoswitch On
**********************************************
when i do vgextend, that the message:

root> / >vgextend vg02 /dev/dsk/c16t0d2
vgextend: Couldn't open physical volume "/dev/rdsk/c14t0d2":
No such device or address
****************************************
And that is the output of the command lssf

root> / >lssf /dev/dsk/c14t0d0
sdisk card instance 14 SCSI target 0 SCSI LUN 0 section 0 at address ??? /dev/dsk/c14t0d0
root> / >lssf /dev/dsk/c12t0d0
sdisk card instance 12 SCSI target 0 SCSI LUN 0 section 0 at address 0/0/10/0/0.1.1.0.0.0.0 /dev/dsk/c12t0d0

Somebody have any idea
What's the problem?
I need help!

10 REPLIES 10
A. Clay Stephenson
Acclaimed Contributor

Re: extending a VG

It means that /dev/rdsk/c14t0d2 cannot be accessed (probably a failed disk). Do an ioscan -C disk -fn and check to see if the disk is POWERFAILED.
If it ain't broke, I can fix that.
Svetoslav Gyurov
Valued Contributor

Re: extending a VG

Hi,

I suppouse that this is a SAN configuration ? Are you using SecurePath ? By some reason it seems that your virtual disks are not available any more. Try to run vgscan to see if the disks are available at new hardware paths and paste ioscan -fnCdisk ?

Regards.


--
sve
IT_2007
Honored Contributor

Re: extending a VG

before you run vgscan do these things.

1. mv /etc/lvmtab /tmp/lvmtab.orig
2. vgscan -av

Fix any errors pops up. If you still not able to fix them then there might be Hardware issues.
James R. Ferguson
Acclaimed Contributor

Re: extending a VG

Hi:

The disk at '/dev/rdsk/c14t0d2' may have failed. Do:

# ioscan -fnC disk

...and insure taht the device is "CLAIMED". Also see if you can get output (particularly a viable size) from:

# diskinfo /dev/rdsk/c14t0d2

Verify, too, that you can read the device without errors:

# dd if=/dev/rdsk/c14t0d2 of=/dev/null bs=1024k count=100

Regards!

...JRF...
Feljav
Frequent Advisor

Re: extending a VG

I can't see any information of the disk
/dev/dsk/c14t0d2
/dev/dsk/c14t0d1
/dev/dsk/c14t0d3

when i use the command diskinfo.
What can I do?
Svetoslav Gyurov
Valued Contributor

Re: extending a VG

Would you describe your infrastructure and paste the result of ioscan -fnC disk ?

Regards.

--
sve
Feljav
Frequent Advisor

Re: extending a VG

That's the output of the command
ioscan -fnC disk

root> / >ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 0 0/0/0/3/0.5.0 sdisk CLAIMED DEVICE HP 36.4GST336752LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 0/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 36.4GST336752LC
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
disk 28 0/0/6/0/0.1.7.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c16t0d0 /dev/rdsk/c16t0d0
disk 29 0/0/6/0/0.1.7.0.0.0.1 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c16t0d1 /dev/rdsk/c16t0d1
disk 30 0/0/6/0/0.1.7.0.0.0.2 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c16t0d2 /dev/rdsk/c16t0d2
disk 31 0/0/6/0/0.1.7.0.0.0.3 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c16t0d3 /dev/rdsk/c16t0d3
disk 32 0/0/6/0/0.1.7.0.0.0.4 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c16t0d4 /dev/rdsk/c16t0d4
disk 18 0/0/10/0/0.1.1.0.0.0.0 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
disk 19 0/0/10/0/0.1.1.0.0.0.1 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c12t0d1 /dev/rdsk/c12t0d1
disk 20 0/0/10/0/0.1.1.0.0.0.2 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c12t0d2 /dev/rdsk/c12t0d2
disk 21 0/0/10/0/0.1.1.0.0.0.3 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c12t0d3 /dev/rdsk/c12t0d3
disk 22 0/0/10/0/0.1.1.0.0.0.4 sdisk CLAIMED DEVICE HP A6189A
/dev/dsk/c12t0d4 /dev/rdsk/c12t0d4
disk 2 0/0/12/0/0.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
Sandman!
Honored Contributor

Re: extending a VG

Looks like the instance number of your alternate path(s) has changed from c14t#d# to c16t#d#. Was any SAN related work done recently in your environment?

Try to see if the VG will recognize the alternate path using "vgchange -a y vg02". Otherwise vgreduce the alternate path and vgextend the current one and run strings on your lvmtab file to see that the PVs are recorded correctly i.e.

# vgchange -a y vg02
OR
# vgreduce vg02 /dev/dsk/c14t0d2
# vgextend vg02 /dev/dsk/c16t0d2
# strings /etc/lvmtab
sathish kannan
Valued Contributor

Re: extending a VG

Hi Feijav,

Looks like the Controller number changed from c14 to c16.

Audit recent changes in your SAN environmnet like switch port change or switch domain ID etc..



Regards
Sathish
Don't Think too much
Yang Qin_1
Honored Contributor

Re: extending a VG

Hi, Feijav,

Apparently c14t#d# is no longer exist on your system. In this case, you may try to use vgscan to re-create /etc/lvmtab.

Save current /etc/lvmtab to another file, run:

vgscan -p -a -v (scan all devices but do not update lvmtab)

vgscan -v -a (create new /etc/lvmtab file)

When new lvmtab is created, c14t#d# will be removed from lvmtab and you can extend that VG.

You may still need to verify the other pathes which replaced c14t#d# and add them back to VGs if they are not there.

Regards,
Yang