- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Removing logical volume has not freed up disk spac...
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
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
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-11-2011 08:53 AM
10-11-2011 08:53 AM
Removing logical volume has not freed up disk space on the volume group
Hi,
I have removed a logical volume from a volume group via SAM but because our /tmp area was full (and SAM needs a bit of space on /tmp to be able to delete a logical volume) it has only removed the entry from fstab and not freed up the disk space on the volume group. I have since manually removed the entries from /dev/"volume-group-name". I restored the entries and then run an lvremove but it came back with the following (the logical volume concerned is lvCAST and the volume group concerned is vgEVA):
# pwd
/dev/vgEVA
# ls -la
total 32
drwxrwxr-x 2 root sys 8192 Oct 6 17:00 .
dr-xr-xr-x 18 bin bin 8192 Oct 10 23:59 ..
crw-rw-r-- 1 root sys 64 0x030000 Jun 7 2010 group
br--r----- 1 root sys 64 0x030005 Oct 6 2010 lvBUSOBJ
br--r----- 1 root sys 64 0x030014 Oct 6 2010 lvCAST
br--r----- 1 root sys 64 0x030003 Oct 6 2010 lvCLICON
brw-r----- 1 root sys 64 0x030007 Jun 7 2010 lvDEVBUSOB
brw-r----- 1 root sys 64 0x030008 Jun 7 2010 lvDEVPTRFN
br--r----- 1 root sys 64 0x030004 Jun 28 2010 lvEAYP
br--r----- 1 root sys 64 0x030002 Oct 6 2010 lvEYFAS
brw-r----- 1 root sys 64 0x030006 Jun 7 2010 lvPRDPTRFN
br--r----- 1 root sys 64 0x030001 Oct 6 2010 lvWHDBS
br--r----- 1 root sys 64 0x030010 Jun 14 2010 lvadmin
br--r----- 1 root sys 64 0x030015 Oct 7 2010 lvarchivelogs
br--r----- 1 root sys 64 0x030013 Oct 6 2010 lvdata
br--r----- 1 root sys 64 0x030012 Jun 14 2010 lvlogs
br--r----- 1 root sys 64 0x030011 Jun 14 2010 lvops
br--r----- 1 root sys 64 0x03000f Jun 14 2010 lvoralogs
br--r----- 1 root sys 64 0x03000e Jun 14 2010 lvproduct
br--r----- 1 root sys 64 0x03000a Jun 14 2010 lvproduction
br--r----- 1 root sys 64 0x030009 Jun 14 2010 lvreports
br--r----- 1 root sys 64 0x03000d Jun 15 2010 lvsafety
br--r----- 1 root sys 64 0x03000c Jun 14 2010 lvsoftware
br--r----- 1 root sys 64 0x03000b Jun 14 2010 lvtrace
cr--r----- 1 root sys 64 0x030005 Oct 6 2010 rlvBUSOBJ
cr--r----- 1 root sys 64 0x030014 Oct 6 2010 rlvCAST
cr--r----- 1 root sys 64 0x030003 Oct 6 2010 rlvCLICON
crw-r----- 1 root sys 64 0x030007 Jun 7 2010 rlvDEVBUSOB
crw-r----- 1 root sys 64 0x030008 Jun 7 2010 rlvDEVPTRFN
cr--r----- 1 root sys 64 0x030004 Jun 28 2010 rlvEAYP
cr--r----- 1 root sys 64 0x030002 Oct 6 2010 rlvEYFAS
crw-r----- 1 root sys 64 0x030006 Jun 7 2010 rlvPRDPTRFN
cr--r----- 1 root sys 64 0x030001 Oct 6 2010 rlvWHDBS
cr--r----- 1 root sys 64 0x030010 Jun 14 2010 rlvadmin
cr--r----- 1 root sys 64 0x030015 Oct 7 2010 rlvarchivelogs
cr--r----- 1 root sys 64 0x030013 Oct 6 2010 rlvdata
cr--r----- 1 root sys 64 0x030012 Jun 14 2010 rlvlogs
cr--r----- 1 root sys 64 0x030011 Jun 14 2010 rlvops
cr--r----- 1 root sys 64 0x03000f Jun 14 2010 rlvoralogs
cr--r----- 1 root sys 64 0x03000e Jun 14 2010 rlvproduct
cr--r----- 1 root sys 64 0x03000a Jun 14 2010 rlvproduction
cr--r----- 1 root sys 64 0x030009 Jun 14 2010 rlvreports
cr--r----- 1 root sys 64 0x03000d Jun 15 2010 rlvsafety
cr--r----- 1 root sys 64 0x03000c Jun 14 2010 rlvsoftware
cr--r----- 1 root sys 64 0x03000b Jun 14 2010 rlvtrace
# lvremove /dev/vgEVA/lvCAST
lvremove: Couldn't delete logical volume "/dev/vgEVA/lvCAST":
The supplied lv number refers to a non-existent logical volume.
Volume Group configuration for /dev/vgEVA has been saved in /etc/lvmconf/vgEVA.conf
# ls -la
total 32
drwxrwxr-x 2 root sys 8192 Oct 6 17:00 .
dr-xr-xr-x 18 bin bin 8192 Oct 10 23:59 ..
crw-rw-r-- 1 root sys 64 0x030000 Jun 7 2010 group
br--r----- 1 root sys 64 0x030005 Oct 6 2010 lvBUSOBJ
br--r----- 1 root sys 64 0x030014 Oct 6 2010 lvCAST
br--r----- 1 root sys 64 0x030003 Oct 6 2010 lvCLICON
brw-r----- 1 root sys 64 0x030007 Jun 7 2010 lvDEVBUSOB
brw-r----- 1 root sys 64 0x030008 Jun 7 2010 lvDEVPTRFN
br--r----- 1 root sys 64 0x030004 Jun 28 2010 lvEAYP
br--r----- 1 root sys 64 0x030002 Oct 6 2010 lvEYFAS
brw-r----- 1 root sys 64 0x030006 Jun 7 2010 lvPRDPTRFN
br--r----- 1 root sys 64 0x030001 Oct 6 2010 lvWHDBS
br--r----- 1 root sys 64 0x030010 Jun 14 2010 lvadmin
br--r----- 1 root sys 64 0x030015 Oct 7 2010 lvarchivelogs
br--r----- 1 root sys 64 0x030013 Oct 6 2010 lvdata
br--r----- 1 root sys 64 0x030012 Jun 14 2010 lvlogs
br--r----- 1 root sys 64 0x030011 Jun 14 2010 lvops
br--r----- 1 root sys 64 0x03000f Jun 14 2010 lvoralogs
br--r----- 1 root sys 64 0x03000e Jun 14 2010 lvproduct
br--r----- 1 root sys 64 0x03000a Jun 14 2010 lvproduction
br--r----- 1 root sys 64 0x030009 Jun 14 2010 lvreports
br--r----- 1 root sys 64 0x03000d Jun 15 2010 lvsafety
br--r----- 1 root sys 64 0x03000c Jun 14 2010 lvsoftware
br--r----- 1 root sys 64 0x03000b Jun 14 2010 lvtrace
cr--r----- 1 root sys 64 0x030005 Oct 6 2010 rlvBUSOBJ
cr--r----- 1 root sys 64 0x030014 Oct 6 2010 rlvCAST
cr--r----- 1 root sys 64 0x030003 Oct 6 2010 rlvCLICON
crw-r----- 1 root sys 64 0x030007 Jun 7 2010 rlvDEVBUSOB
crw-r----- 1 root sys 64 0x030008 Jun 7 2010 rlvDEVPTRFN
cr--r----- 1 root sys 64 0x030004 Jun 28 2010 rlvEAYP
cr--r----- 1 root sys 64 0x030002 Oct 6 2010 rlvEYFAS
crw-r----- 1 root sys 64 0x030006 Jun 7 2010 rlvPRDPTRFN
cr--r----- 1 root sys 64 0x030001 Oct 6 2010 rlvWHDBS
cr--r----- 1 root sys 64 0x030010 Jun 14 2010 rlvadmin
cr--r----- 1 root sys 64 0x030015 Oct 7 2010 rlvarchivelogs
cr--r----- 1 root sys 64 0x030013 Oct 6 2010 rlvdata
cr--r----- 1 root sys 64 0x030012 Jun 14 2010 rlvlogs
cr--r----- 1 root sys 64 0x030011 Jun 14 2010 rlvops
cr--r----- 1 root sys 64 0x03000f Jun 14 2010 rlvoralogs
cr--r----- 1 root sys 64 0x03000e Jun 14 2010 rlvproduct
cr--r----- 1 root sys 64 0x03000a Jun 14 2010 rlvproduction
cr--r----- 1 root sys 64 0x030009 Jun 14 2010 rlvreports
cr--r----- 1 root sys 64 0x03000d Jun 15 2010 rlvsafety
cr--r----- 1 root sys 64 0x03000c Jun 14 2010 rlvsoftware
cr--r----- 1 root sys 64 0x03000b Jun 14 2010 rlvtrace
I have also a run a vgscan to no avail. Is there anything else I can do other than ultimately removing the logical volumes and volume group and recreating it all (taking a backup first of all of course!).
Kind Regards - Mark P.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 08:58 AM
10-11-2011 08:58 AM
Re: Removing logical volume has not freed up disk space on the volume group
Does a 'vgdisplay -v vgEVA' still show that LV as part of the VG? Can you do an 'lvdisplay /dev/vgEVA/lvCAST'?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 09:13 AM
10-11-2011 09:13 AM
Re: Removing logical volume has not freed up disk space on the volume group
Yes x 2:
vgdisplay -v vgEVA
LV Name /dev/vgEVA/lvCAST
LV Status available/syncd
LV Size (Mbytes) 0
Current LE 0
Allocated PE 0
Used PV 0
# lvdisplay /dev/vgEVA/lvCAST
--- Logical volumes ---
LV Name /dev/vgEVA/lvCAST
VG Name /dev/vgEVA
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 0
Current LE 0
Allocated PE 0
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation non-strict
IO Timeout (Seconds) default
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 11:03 AM
10-11-2011 11:03 AM
Re: Removing logical volume has not freed up disk space on the volume group
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2011 06:52 AM
10-12-2011 06:52 AM
Re: Removing logical volume has not freed up disk space on the volume group
--- Volume groups ---
VG Name /dev/vgEVA
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 20
Open LV 21
Max PV 16
Cur PV 6
Act PV 6
Max PE per PV 6400
VGDA 12
PE Size (Mbytes) 4
Total PE 38388
Alloc PE 33388
Free PE 5000
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vgEVA/lvWHDBS
LV Status available/syncd
LV Size (Mbytes) 36000
Current LE 9000
Allocated PE 9000
Used PV 3
LV Name /dev/vgEVA/lvEYFAS
LV Status available/syncd
LV Size (Mbytes) 25000
Current LE 6250
Allocated PE 6250
Used PV 3
LV Name /dev/vgEVA/lvCLICON
LV Status available/syncd
LV Size (Mbytes) 15000
Current LE 3750
Allocated PE 3750
Used PV 1
LV Name /dev/vgEVA/lvEAYP
LV Status available/syncd
LV Size (Mbytes) 15000
Current LE 3750
Allocated PE 3750
Used PV 1
LV Name /dev/vgEVA/lvBUSOBJ
LV Status available/syncd
LV Size (Mbytes) 10000
Current LE 2500
Allocated PE 2500
Used PV 3
LV Name /dev/vgEVA/lvPRDPTRFN
LV Status available/syncd
LV Size (Mbytes) 2200
Current LE 550
Allocated PE 550
Used PV 1
LV Name /dev/vgEVA/lvDEVBUSOB
LV Status available/syncd
LV Size (Mbytes) 3712
Current LE 928
Allocated PE 928
Used PV 1
LV Name /dev/vgEVA/lvDEVPTRFN
LV Status available/syncd
LV Size (Mbytes) 2400
Current LE 600
Allocated PE 600
Used PV 1
LV Name /dev/vgEVA/lvreports
LV Status available/syncd
LV Size (Mbytes) 252
Current LE 63
Allocated PE 63
Used PV 1
LV Name /dev/vgEVA/lvproduction
LV Status available/syncd
LV Size (Mbytes) 1600
Current LE 400
Allocated PE 400
Used PV 1
LV Name /dev/vgEVA/lvtrace
LV Status available/syncd
LV Size (Mbytes) 500
Current LE 125
Allocated PE 125
Used PV 1
LV Name /dev/vgEVA/lvsoftware
LV Status available/syncd
LV Size (Mbytes) 5000
Current LE 1250
Allocated PE 1250
Used PV 1
LV Name /dev/vgEVA/lvsafety
LV Status available/syncd
LV Size (Mbytes) 500
Current LE 125
Allocated PE 125
Used PV 1
LV Name /dev/vgEVA/lvproduct
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 3000
Allocated PE 3000
Used PV 2
LV Name /dev/vgEVA/lvoralogs
LV Status available/syncd
LV Size (Mbytes) 300
Current LE 75
Allocated PE 75
Used PV 1
LV Name /dev/vgEVA/lvadmin
LV Status available/syncd
LV Size (Mbytes) 252
Current LE 63
Allocated PE 63
Used PV 1
LV Name /dev/vgEVA/lvops
LV Status available/syncd
LV Size (Mbytes) 252
Current LE 63
Allocated PE 63
Used PV 1
LV Name /dev/vgEVA/lvlogs
LV Status available/syncd
LV Size (Mbytes) 252
Current LE 63
Allocated PE 63
Used PV 1
LV Name /dev/vgEVA/lvdata
LV Status available/syncd
LV Size (Mbytes) 1000
Current LE 250
Allocated PE 250
Used PV 1
LV Name /dev/vgEVA/lvCAST
LV Status available/syncd
LV Size (Mbytes) 0
Current LE 0
Allocated PE 0
Used PV 0
LV Name /dev/vgEVA/lvarchivelogs
LV Status available/syncd
LV Size (Mbytes) 2332
Current LE 583
Allocated PE 583
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c40t0d5
PV Status available
Total PE 6398
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c40t0d6
PV Status available
Total PE 6398
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c40t0d7
PV Status available
Total PE 6398
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c40t1d0
PV Status available
Total PE 6398
Free PE 1092
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c40t1d1
PV Status available
Total PE 6398
Free PE 2333
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c40t1d2
PV Status available
Total PE 6398
Free PE 1575
Autoswitch On
Proactive Polling On
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2011 05:08 AM
10-17-2011 05:08 AM
Re: Removing logical volume has not freed up disk space on the volume group
Bounce!