Operating System - HP-UX
1837183 Members
3216 Online
110113 Solutions
New Discussion

Cannot vgreduce failed devices

 
Tuck Lee
Frequent Advisor

Cannot vgreduce failed devices

I need some help from this error messages. I cannot do a vgreduce with -f and -l

dmesg...
read_efi_hdr: physio failed
read_efi_hdr: physio failed
read_efi_hdr: physio failed
read_efi_hdr: physio failed
read_efi_hdr: physio failed
read_efi_hdr: physio failed
LVM: VG 64 0x030000: Lost quorum.
This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
<31 0x140000>
LVM: VG 64 0x030000: Reestablished quorum.
ipmi_wd_heartbeat(): timer not refreshed.
ipmi_wd_heartbeat(): Reestablished communication with BMC
ipmi_wd_heartbeat(): timer not refreshed.
ipmi_wd_heartbeat(): Reestablished communication with BMC

vgdisplay...
--- Physical volumes ---
PV Name /dev/dsk/c20t0d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c31t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c21t0d0":
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 15997
Free PE 1
Autoswitch On

vgreduce -f /dev/vgbackup1
vgreduce: Couldn't query physical volume "/dev/dsk/c31t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgreduce: Couldn't query physical volume "/dev/dsk/c21t0d0":
The specified path does not correspond to physical volume attached to
this volume group

vgreduce -l /dev/vgbackup1 /dev/dsk/c31t0d0
vgreduce: "/dev/dsk/c31t0d0": No such file or directory

strings /etc/lvmtab ...
/dev/vgbackup1
/dev/dsk/c20t0d0
/dev/dsk/c31t0d0
/dev/dsk/c21t0d0
14 REPLIES 14
Aneesh Mohan
Honored Contributor

Re: Cannot vgreduce failed devices

Hi,

Please post
#vgdisplay -v /dev/vgbackup1

I feel some LE are allocated with /dev/dsk/c21t0d0 and the disk/path is not existing .

Aneesh
Johnson Punniyalingam
Honored Contributor

Re: Cannot vgreduce failed devices

vgdisplay -v /dev/vgbackup1 |more --> can post output also please check

pv is avaible _not_available


Example :-
PV Status available

Problems are common to all, but attitude makes the difference
Sreejith Kaliyam
Regular Advisor

Re: Cannot vgreduce failed devices

Ofcourse, "/dev/dsk/c31t0d0" will not be available But am suspecting there are some PE`s still allocated from the device .It has to cleanup before doing vgreduce.

Please post vgdisplay -v vgbackup1.

Aneesh
Tuck Lee
Frequent Advisor

Re: Cannot vgreduce failed devices

The vgdisplay -v /dev/vgbcakup1 is clean but the lvmtab is not. How do I clean up the lvmtab?

--- Volume groups ---
VG Name /dev/vgbackup1
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 64000
VGDA 2
PE Size (Mbytes) 16
Total PE 15997
Alloc PE 15996
Free PE 1
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vgbackup1/lvbackup1
LV Status available/syncd
LV Size (Mbytes) 255936
Current LE 15996
Allocated PE 15996
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c20t0d0
PV Status available
Total PE 15997
Free PE 1
Autoswitch On


.....
/dev/vgbackup1
/dev/dsk/c20t0d0
/dev/dsk/c31t0d0
/dev/dsk/c21t0d0

Johnson Punniyalingam
Honored Contributor

Re: Cannot vgreduce failed devices

>>>The vgdisplay -v /dev/vgbcakup1 is clean but the lvmtab is not. How do I clean up the lvmtab? <<<

Looks like you lvmtab not been updated properly

# mv /etc/lvmtab /etc/lvmtab.bk
# vgscan -a -> this create new lvmtab


Thanks,
Johnson
Problems are common to all, but attitude makes the difference
Johnson Punniyalingam
Honored Contributor

Re: Cannot vgreduce failed devices

Hi dude,

could you assign the points. Once your problem is resolved

for poeple given their valuable time to provide the solution.

Thanks & Regards,

Johnson
Problems are common to all, but attitude makes the difference
Tuck Lee
Frequent Advisor

Re: Cannot vgreduce failed devices

Hi, Just like to confirm one thing, when I do a vgscan -a, will it cause device to be renamed? I have not use this command before and I would like to make sure that it will not cause and device name to be changed.

Johnson Punniyalingam
Honored Contributor

Re: Cannot vgreduce failed devices

>>vgscan -a, will it cause device to be renamed? I have not use this command before and I would like to make sure that it will not cause and device name to be changed.<<<

no change will be updated ,

rebuilding the new lvmtab file,

normal if your lvmtab corrupted we will do "vgscan"

cp -pi /etc/lvmtab /etc/lvmtab.old

vgscan -v

vgscan -a
Problems are common to all, but attitude makes the difference
Tuck Lee
Frequent Advisor

Re: Cannot vgreduce failed devices

Hi
no luck , the vgscan -... did not remove the dev from the lvmtab but give this error. When I do vgreduce as follows, it give me error

vgreduce -l /dev/vgbackup1 /dev/dsk/c31t0d0
vgreduce: "/dev/dsk/c31t0d0": No such file or directory
Johnson Punniyalingam
Honored Contributor

Re: Cannot vgreduce failed devices

>> vgreduce -l /dev/vgbackup1 /dev/dsk/c31t0d0
vgreduce: "/dev/dsk/c31t0d0": No such file or directory<<

vgchange -a n /dev/vgbackup1 - can you try to deactivate it ..?

vgreduce /dev/vgbackup1 /dev/dsk/c31t0d0

vgdisplay -v /dev/vgbackup1 |more --> Need output


strings /etc/lvmtab --> Need output
Problems are common to all, but attitude makes the difference
Safarali
Valued Contributor

Re: Cannot vgreduce failed devices

Hi Tuck

vgreduce -l /dev/dsk/c31t0d0 /dev/vgbackup1

Please let me know the result


Regards
Safar
Tuck Lee
Frequent Advisor

Re: Cannot vgreduce failed devices

Hi,

Same bad result # vgreduce -l /dev/dsk/c31t0d0 /dev/vgbackup1
vgreduce: "/dev/vgbackup1": No such file or directory
Usage: vgreduce
[-A Autobackup]
[-l]
VolumeGroupName PhysicalVolumePath... | [-f] VolumeGroupName
The syntax is wrong i believe!
Safarali
Valued Contributor

Re: Cannot vgreduce failed devices

export the vg and import it back it looks like device file is not exisiting


Regards

Safar

Johnson Punniyalingam
Honored Contributor

Re: Cannot vgreduce failed devices

>>>Same bad result # vgreduce -l /dev/dsk/c31t0d0 /dev/vgbackup1
vgreduce: "/dev/vgbackup1": No such file or directory
Usage: vgreduce
[-A Autobackup]
[-l]
VolumeGroupName PhysicalVolumePath... | [-f] VolumeGroupName
The syntax is wrong i believe!>>

Yes Syntax is wrong.

vgreduce -l

man vgreduce,

Thanks,
Johnson
Problems are common to all, but attitude makes the difference