- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Safe to delete /etc/lvmconf/vg*conf.old files?
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
07-06-2008 11:07 PM
07-06-2008 11:07 PM
I am a bit tight with disk space in / on this box.
I looked for candidates of files which possibly could be removed and found quite a few lvmconf backup files in /etc/lvmconf which take up considerable amount of space.
I wonder if it was safe to remove those with the .old extensions.
If I look at what vgcfgrestore outputs if applied on those the only difference seems to be in the first line where the deviating name of the backup file with .old suffix appears.
[root@warnow(Z01):/etc/lvmconf]
# vgcfgrestore -l -f vgsapz01.conf.old|sed -n 2,\$p|cksum
1663276796 1135
[root@warnow(Z01):/etc/lvmconf]
# vgcfgrestore -l -f vgsapz01.conf|sed -n 2,\$p|cksum
1663276796 1135
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2008 11:24 PM
07-06-2008 11:24 PM
Re: Safe to delete /etc/lvmconf/vg*conf.old files?
Why not link /etc/lvmconf to new filesystem inside vg00 (if you have enough space).
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2008 11:29 PM
07-06-2008 11:29 PM
Re: Safe to delete /etc/lvmconf/vg*conf.old files?
You may also save them anywhere else.
Anyway, normally you'll save a couple of kb only (unless you have very large LVM configs).
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
07-06-2008 11:29 PM
07-06-2008 11:29 PM
Re: Safe to delete /etc/lvmconf/vg*conf.old files?
$ /usr/sbin/vgdisplay vg00|grep -e Size -e Free
PE Size (Mbytes) 8
Free PE 844
$ echo $((8*422))
3376
But I thought that contents of /etc/lvmconf needed to be integral part of /dev/vg00/lvol3 (e.g. in maintenance mode)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2008 11:32 PM
07-06-2008 11:32 PM
Re: Safe to delete /etc/lvmconf/vg*conf.old files?
You can also check the contents, for example:
# vgcfgrestore -f /etc/lvmconf/vg00.conf.old -l
Volume Group Configuration information in "/etc/lvmconf/vg00.conf.old"
VG Name /dev/vg00
---- Physical volumes : 1 ----
/dev/rdsk/c0t6d0 (Bootable)
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
07-06-2008 11:35 PM
07-06-2008 11:35 PM
Re: Safe to delete /etc/lvmconf/vg*conf.old files?
haven't done not many LVM changes in the past on this box.
But because there are shared VGs with many SAN PVs only the backup files come close to 22 MB,
which is more than 10% of /.
[root@warnow(Z01):/root]
# ll /etc/lvmconf/*old|awk '$5>0{s+=$5};END{printf"%10.2f\n",s/2^20}'
21.87
I will relocate the /etc/lvmconf/*old files to another filesystem and remove them from here.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2008 11:37 PM
07-06-2008 11:37 PM
Re: Safe to delete /etc/lvmconf/vg*conf.old files?
see my cksums above.
The outputs only differ in the 1st line with the conf file name (certainly).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2008 04:08 AM
07-07-2008 04:08 AM
SolutionBy default every time an LVM modification is made a 'vgcfgbackup' is run. Too, when an Ignite recovery backup is made, 'vgcfgbackup' is run.
If you are short on space, I think you can quite safely remove the ".old" files. After all, if you needed to perform a 'vgcfgrestore' you would be using the most current backup.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2008 04:15 AM
07-07-2008 04:15 AM
Re: Safe to delete /etc/lvmconf/vg*conf.old files?
that was it, I hadn't Ignite on the agenda.
Now I know where the backup files originate from.
Thanks for the reminder.