In the past, an optimum scenario would be to create a raw partition (less than 100MB) to have a "heartbeat".
System 1 would own the external dasd, and periodically check in to the raw partition (timestamp), as would system 2 (simutaenously) when system 1 goes down or crashes on way or another system 2 would see that evident at the raw partition then STONITH (Shoot The Other Node In The Head) and take over whatever job it was doing. Dean Price [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Tarus Balog said: > Gang: > > Okay, I want to make a particular file system highly available. > > For example, suppose, just suppose, I had a directory called > "/var/opennms" that I wanted multiple machines to be able to write to. > So if I had two active machines writing to that file system, and one > died, I'd have a third machine that could come on-line and pick up > where the failed machine left off. > > It has to be fast and reliable (so nothing like NFS). Has anyone worked > with SAN equipment where we could dual attach two or more machines over > SCSI or Fiber Channel? > > How do Linux Clusters handle making data highly available. > > Relevant links and RTFM suggestions welcome. > > -T > > ________________________________________________________________________ > ___ > Tarus Balog, OpenNMS Maintainer Main: +1 919 545 2553 > Blast Internet Services, Inc. Fax: +1 503-961-7746 > Email: [EMAIL PROTECTED] URL: > http://www2.blast.com/tarus > PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C > > -- > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ : http://trilug.org/faq/ > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ > TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc > -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
