Re: Please name new maintainers
John Lange <[email protected]> Wed, 05 Dec 2007 03:59:01 -0600
| Newsgroups | gmane.linux.evms.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2007-12-05 at 07:49 +0100, Dirk Heinrichs wrote: > > Plus, we used the evms disk spanning (or whatever it's called) to make > > all the LUNs on the SAN appear as one device. > > Drive link. Bad idea. You could have simply added them to a existing VG > later. Now you tell me ;) > So, if I got it right, you used the drivelink feature to create one big > device, and then put logical volumes on top of that? In this case, yes, you > would have to backup and start from scratch. Yup. That is what I thought. > But, I think I wrote it in an earlier thread: The fact that EVMS is > currently unmaintained doesn't mean it stops working. So as long as it > works fine for you the way it's setup now, there is no reason for you to > switch. EVMS does not work reliably the way it is now. We have a 4 node cluster sharing the SAN using EVMS and OCFS2 all this powered by heartbeat. At the moment only one node can start EVMS at a time. The rest do not display the devices in /dev/evms and therefore can not mount the drives or participate in the cluster. evms has been a headache from the start and we deeply regret using it (I blame Novell who recommended it in a whitepaper). Even if it was being maintained I'd urge others to steer clear of it. John ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Evms-devel mailing list [email protected] To subscribe/unsubscribe, please visit: https://lists.sourceforge.net/lists/listinfo/evms-devel