On 2005-11-16 11:08:51 +0000, Julian Smith wrote:
> One way of handling this would be to write a filesystem that copies the
> contents of modified files over a network before close() returns. That
> way, as long as a SMTP server (say) checks the return from close()
> before telling the sender that it has received everything ok, we can
> avoid any single point of failure. If the data is copied to all the
> other machines in a CARP `family', then we should end up with perfectly
> syncronised machines, each of which can take over at any time. The
> obvious downside is potential speed problems.
Check out DRBD. Remote, shared RAID1. Sadly, it's Linux only.
Best
Martin
--
http://www.tm.oneiros.de
