We use HA-LVM in environments where we do not use GFS. It works well in preventing shared storage from being mounted on both nodes simultaneouly. However I am not sure how it would react in a split brain conditon, which appears to be what you are describing. . You should probably consider creating redundancy in your heartbeat via IP Bonding. Basically having two nics on each host bound to one ip. Sent via BlackBerry by AT&T -----Original Message----- From: linux-cluster-request@xxxxxxxxxx Date: Sun, 23 Aug 2009 12:00:08 To: <linux-cluster@xxxxxxxxxx> Subject: Linux-cluster Digest, Vol 64, Issue 37 Send Linux-cluster mailing list submissions to linux-cluster@xxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/linux-cluster or, via email, send a message with subject or body 'help' to linux-cluster-request@xxxxxxxxxx You can reach the person managing the list at linux-cluster-owner@xxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-cluster digest..." Today's Topics: 1. Preventing LVM from concurrent access (Edson Marquezani Filho) ---------------------------------------------------------------------- Message: 1 Date: Sun, 23 Aug 2009 12:35:39 -0300 From: Edson Marquezani Filho <edsonmarquezani@xxxxxxxxx> Subject: Preventing LVM from concurrent access To: linux-cluster@xxxxxxxxxx Message-ID: <2fc5f090908230835p20acd5e0ya2bd2a3ba909350b@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 Hello, I'm a begginer on that cluster stuff, so I ask you for help. I'm setting up a environment with virtual machines running upon Xen, two servers, and a SAN storage. I want to set up a very simple high-availability scenario, where once my master server goes down, slave creates again those virtual machines on it. (What would correspond to a restart of all machines, off course.) Ok, I could do that with Heartbeat, with a very simple configuration based on its version 1. It worked as expected. My problem now is related to SAN data access. I want to prevent data to be simultaneously mounted by both servers, in a situation when I don't have master server down, altough it could look like this. I'm connecting servers through a crossover UTP cable. If it get disconnected or any of those dedicated interfaces goes down, slave server would think that master server is down, and would recreate all my virtual machines, altough it isn't down, corrupting LVM and filesystem data. Alright, I have found out that I would have to use either HA-LVM or CLVMD. Actually, I think that HA-LVM would be more appropriate to me, accordingly to what I've seen around. But, I'm really not sure about that. What should I use, exactly? Does HA-LVM do what I want? Does it prevent LVM volumes from being mounted by more than a node simultaneously? I have thought about locking VGs on each server, with CLMD, but I'm not sure if it is the correct way for that. I can say for sure that I just need data access at one server at a time. What would be the simplest and more correct way for doing this? Thank you. ------------------------------ -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster End of Linux-cluster Digest, Vol 64, Issue 37 ********************************************* -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
