- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgreduce won't work, physical extents in use s...
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
Discussions
Discussions
Forums
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
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
тАО10-15-2002 07:19 AM
тАО10-15-2002 07:19 AM
Re: vgreduce won't work, physical extents in use supposedly
vgreduce: Invalid LVMREC on Physical Volume /dev/rdsk/c0t0d2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 07:35 AM
тАО10-15-2002 07:35 AM
Re: vgreduce won't work, physical extents in use supposedly
So the vgreduce failed again . Usually an invaled LVMREC means that there is a bad header , maybe because of a bad disk . To ensure that a LUN is not bad do this ,
#dd if=/dev/rdsk/c0t0d2 of=/dev/null bs=1024 count=20
and see if number of record in and out are equal . IF not then you are dealing with a bad disk . In that case replace the disk , run a vgcfgrestore and then vgreduce .
Or just replace it , pvcreate it and then use vgreduce -f .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 07:45 AM
тАО10-15-2002 07:45 AM
Re: vgreduce won't work, physical extents in use supposedly
Try running vgreduce -f , while its is powered on .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 07:48 AM
тАО10-15-2002 07:48 AM
Re: vgreduce won't work, physical extents in use supposedly
The pvdisplay still shows 250 PE allocated as before.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 08:01 AM
тАО10-15-2002 08:01 AM
Re: vgreduce won't work, physical extents in use supposedly
Since you want to get rid of the disk, how about trying the vgcfgrestore to it just to see if that cleans up the LVM info on it? Nothing to lose if it doesn't work, right?
JP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 08:08 AM
тАО10-15-2002 08:08 AM
Re: vgreduce won't work, physical extents in use supposedly
vgexport the entire VG into a map file .
# vgchange -a n /dev/vg01
# vgexport -m
This should also remove /dev/vg01 directory .
Recreate /dev/vg01 directory .
#mknod /dev/vg01/group c 64 0xabcdef
Where abcdef is in hex and unique to your system .
Then vgimport VG01 on to all disks .
#vgimport -m
vgimport should recreate the damaged headers .
#vgchnage -a y /dev/vg01 .
Then use vgreduce on that disk .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 08:58 AM
тАО10-15-2002 08:58 AM
Re: vgreduce won't work, physical extents in use supposedly
Ashwani, I'll have to schedule downtime to try the vgexport/vgimport method which I was trying to avoid.
Yes, all I need to do is delete this LUN and we will be removing this array entirely from our system. So it's not an issue that's critical but it would be great to get it cleaned up so we could remove the old array.
I'll award points after I see if anyone else comes up with ideas.
Thanks for the suggestions guys and anyone else who may come up with another option!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 09:52 AM
тАО10-15-2002 09:52 AM
Re: vgreduce won't work, physical extents in use supposedly
What happens if you try to create a new LV using all the PEs on that disk? If it complains about not having enough PEs, try making the LV with 250 PEs less than the max. If that works, maybe a pvdisplay -v will at least show you which 250 PEs it thinks are in use as they won't have your new LV assigned to them.
I just love playing with stuff that is broken, especially when it is on somebody elses system! ;)
JP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 10:32 AM
тАО10-15-2002 10:32 AM
Re: vgreduce won't work, physical extents in use supposedly
--- Physical volumes ---
PV Name /dev/dsk/c0t0d2
VG Name /dev/vg01
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 4
Total PE 7226
Free PE 65286
Allocated PE 4294909236
Stale PE 0
IO Timeout (Seconds) default
--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg01/TESTlv 7226 7226
--- Physical extents ---
PE Status LV LE
0000 current /dev/vg01/TESTlv 0000
0001 current /dev/vg01/TESTlv 0001
0002 current /dev/vg01/TESTlv 0002
........
7222 current /dev/vg01/TESTlv 7222
7223 current /dev/vg01/TESTlv 7223
7224 current /dev/vg01/TESTlv 7224
7225 current /dev/vg01/TESTlv 7225
I then removed the logical volume again which brought me back to square one:
--- Physical volumes ---
PV Name /dev/dsk/c0t0d2
VG Name /dev/vg01
PV Status available
Allocatable yes
VGDA 2
Cur LV 0
PE Size (Mbytes) 4
Total PE 7226
Free PE 6976
Allocated PE 250
Stale PE 0
IO Timeout (Seconds) default
--- Physical extents ---
PE Status LV LE
0000 free 0000
0001 free 0000
0002 free 0000
0003 free 0000
0004 free 0000
0005 free 0000
So the system still thinks there is 250 PE allocated and there isn't. This is getting to be quite an annoying problem. Any other ideas John or some else??? I just want to blow this LUN away anyway we can do it.
Thanks again, Tom.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2002 10:56 AM
тАО10-15-2002 10:56 AM
Re: vgreduce won't work, physical extents in use supposedly
When you powered off that disk and did the vgreduce -f it gave you the invalid LVMREC error. Here is what you could try, but I wouldn't recommend it unless you can take a chance on crashing something. I suggest doing a pvcreate -f on that disk, which should write new LVM structures to it. Then, power it off and try the vgreduce -f on it. Maybe the pvcreate will give it a clean LVMREC and make it happy enough for the vgreduce -f to work.
That is a pretty crazy solution, and like I said, I wouldn't try it unless you've got things backed up good and you can chance crashing things. Otherwise, I guess you have to get some downtime and try the vgexport/vgimport. Are you logging any errors for that disk in syslog or from EMS?
JP
- « Previous
-
- 1
- 2
- Next »