<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> I have been googling this for a while and couldn't find enough important info, but I think you finally gave me my google search term I needed: *transparent* nfs failover. Thanks, I will report any new findings, but I think I am starting to understand why this didn't work. Somehow heartbeat / pacemaker setups have a way to overcome this, but I was merely looking for a manual failover to dual All-In-One boxes. <div class="moz-cite-prefix">On 11/8/2013 11:25 AM, Michael Rasmussen wrote: </div> <blockquote cite="mid:20131108182531.2f032f8e@sleipner.datanom.net" type="cite"> <pre wrap="">On Fri, 08 Nov 2013 12:15:11 -0500 Chris Siebenmann <a class="moz-txt-link-rfc2396E" href="mailto:cks@cs.toronto.edu"><cks@cs.toronto.edu></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> Transparent NFS failover is extremely demanding about the two versions of the filesystems being absolutely identical down to extremely low level details. It's not clear to me if zfs send and zfs recv replicate all of these low-level details; they are certainly not documented to do so. </pre> </blockquote> <pre wrap="">There is also the problem of NFS file locks which cannot be transferred to another server. </pre> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ OmniOS-discuss mailing list <a class="moz-txt-link-abbreviated" href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a> <a class="moz-txt-link-freetext" href="http://lists.omniti.com/mailman/listinfo/omnios-discuss">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a> </pre> </blockquote> </body> </html>