First, let's clarify terminology: a) there is no such thing as an "LVM name". LVM is Logical Volume Manager - it is the toolset to manage volumes b) there are VGs (Volume Groups), LVs (Logical volumes) and PVs (Physical Disks) that make up your LVM configuration c) one or more PVs are collected into a VG, which can then be carved into 1 or more LVs
Second, are all your physical hosts in a cluster? If not, why can they see all the SAN LUNs? That is what SAN zoning and security is for! You don't want a server to be able to see LUNs that aren't for use by that server. And if they are clustered, I would think you should be using a cluster-aware volume manager to deal with that. Kevin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Torrie Sent: Friday, March 11, 2011 11:49 AM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] Prevent LVM on SAN belonging to virtual machine autoconfiguring on other hosts? On 03/11/2011 11:59 AM, solarflow99 wrote: > can you create a LV for each VM and name it after the VM's hostname? or do > you mean there is a conflict with physical hosts and the PV? I have no idea how to name LVMs. The LVMs wer set up by the installer. What I mean is that if I reboot any physical host that's attached to the fabric, the init process tries to autoconfigure any and all volumes that happen to live on the various SAN volumes (since each host can see all the volumes on the SAN). Hope that makes sense. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
