Keep in mind that LVM's are unique to a Linux guest. If a volume is to be mounted in another system then it can't when an LVM with the same name already exists.
Our cloning procedures want to mount a new system in our maintenance Linux guest. This means that the base system (at least /, /etc and /var) cannot live in an LVM. If it was we would get duplicate LVM names. That would make that cloning procedure more difficult, and (emergency) maintenance as well. Last month I had to copy data from an old guest to the new machine. Unfortunately part of the user data was created in an lv within the rootvg group. When I tried to mount that old data it failed because the rootvg was already online in the new machine. That rootvg normally only contains /var, opt, /usr and such. I don't particularly like the base system in LVM, because of the above mentioned reason. On the other hand, it does make it easier to expand filesystems, /usr for example. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael Weiner Sent: Tuesday, August 23, 2016 2:18 PM To: LINUX-390@VM.MARIST.EDU Subject: Creating root LVM Good morning all, I was having a little debate yesterday and I want to get the experts on this list opinions. What's the best practice when it comes to the root directory? Is it acceptable and recommend to create an vgroot and lvroot so it is expandable? Or is it recommended to have the root directory as a regular directory and not expandable. Thank you! Sent from my iPhone Sent from my iPhone ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
