- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Cannot vgreduce failed devices
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2008 02:00 AM
11-01-2008 02:00 AM
Cannot vgreduce failed devices
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2008 02:05 AM
11-01-2008 02:05 AM
Re: Cannot vgreduce failed devices
Please post
#vgdisplay -v /dev/vgbackup1
I feel some LE are allocated with /dev/dsk/c21t0d0 and the disk/path is not existing .
Aneesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2008 02:18 AM
11-01-2008 02:18 AM
Re: Cannot vgreduce failed devices
pv is avaible _not_available
Example :-
PV Status available
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2008 02:26 AM
11-01-2008 02:26 AM
Re: Cannot vgreduce failed devices
Please post vgdisplay -v vgbackup1.
Aneesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2008 05:16 PM
11-02-2008 05:16 PM
Re: Cannot vgreduce failed devices
--- 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2008 09:16 PM
11-02-2008 09:16 PM
Re: Cannot vgreduce failed devices
Looks like you lvmtab not been updated properly
# mv /etc/lvmtab /etc/lvmtab.bk
# vgscan -a -> this create new lvmtab
Thanks,
Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2008 09:26 PM
11-02-2008 09:26 PM
Re: Cannot vgreduce failed devices
could you assign the points. Once your problem is resolved
for poeple given their valuable time to provide the solution.
Thanks & Regards,
Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2008 10:42 PM
11-02-2008 10:42 PM
Re: Cannot vgreduce failed devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2008 11:05 PM
11-02-2008 11:05 PM
Re: Cannot vgreduce failed devices
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2008 08:00 PM
11-05-2008 08:00 PM
Re: Cannot vgreduce failed devices
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2008 08:27 PM
11-05-2008 08:27 PM
Re: Cannot vgreduce failed devices
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2008 08:44 PM
11-05-2008 08:44 PM
Re: Cannot vgreduce failed devices
vgreduce -l /dev/dsk/c31t0d0 /dev/vgbackup1
Please let me know the result
Regards
Safar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2008 10:09 PM
11-05-2008 10:09 PM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2008 10:16 PM
11-05-2008 10:16 PM
Re: Cannot vgreduce failed devices
Regards
Safar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2008 10:24 PM
11-05-2008 10:24 PM
Re: Cannot vgreduce failed devices
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