https://tanguy.ortolo.eu/blog/article72/naming-vgs en a blog about Debian and self-hosting Sat, 09 Feb 2013 00:20:00 +0000 PluXml https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1360369252-1 https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1360369252-1 This may work for desktops but it's a really confusing and bad idea when you start dealing with virtual machines because when you clone a virtual machine the clone's volume groups now have the names of the WRONG server. This drives me nuts that the installers for debian sets this as the default. Sat, 09 Feb 2013 00:20:00 +0000 sdawg https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347976298-1 https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347976298-1 You can always use vgrename to rename your VGs in case of conflict. I usually stick to 'sys' and 'data' VGs regardless of machine name or purpose, and use vgrename when recovery is needed. Tue, 18 Sep 2012 13:51:00 +0000 Ernesto Hernández-Novich https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347963860-1 https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347963860-1 RHEL started doing the same since 6. Before that it was VolGroup00 etc. Tue, 18 Sep 2012 10:24:00 +0000 Ewoud Kohl van Wijngaarden https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347910137-1 https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347910137-1 Note that for example the Debian Installer will by default name the volume group after the hostname. Mon, 17 Sep 2012 19:28:00 +0000 Joachim Breitner https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347905443-1 https://tanguy.ortolo.eu/blog/article72/naming-vgs/#c1347905443-1 This is so right :) Building a machine - something like /lvm/server1/webmiror makes a lot of sense - you can see immediately what the volume name actually means. Mon, 17 Sep 2012 18:10:00 +0000 Andy Cater