On Mon, Jun 12, 2006 at 03:21:28PM -0700, Carl Lowenstein wrote: > Sanity check time. I hope you aren't trying to push changes to any > specific file in both directions. It seems to me that the only way > you can avoid some peculiar loop or deadlock conditions is to start by > specifying that only computer A can write to file system A, and > computer B can write to file system B. But both computers can read > both file systems.
Here's the scoop... one web server serves content from one NAS, and another web server serves content from the other. So, each NAS has, for example: Share1 Share2 Share3 Share4 One one NAS, Share1 is used, and the others are empty shares. On the other, Share1 is an empty share and 2,3 & 4 are used. I want the currently-unused Share1 on the one NAS to always be a mirror of Share1 on the other NAS, and vice-versa for the other shares. So, no, changes are always supposed to go one way. And there probably won't be a whole lot of changes to existing files... but there will be more and more files added over time. I've given up on hot-failover with these NASes. I'll just be happy if, in the event that NAS1 fails, I can just kill off dead NFS processes and remout all shares from NAS2. -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
