I have been asked about this scenario, with a "roll their own" failover 
scenario.  S10u5  -- I think, at least 127127-11 kernel patch). 0

They have shared storage setup (a shared 3510) with ZFS, and when trying 
to failover they run (aside from migrating the server's IP):

   server1 (failing):        unshare /mypool
                             zfs export /mypool

   node2 (newly online):     zfs import /mypool
                             share /mypool

After that the unsuspecting client gets nothing but ESTALE errors when 
trying to read/write previously open files.

Is this something that should work?    I suspect this might be due to 
the fact that zfs_vfsinit() is finding a different major number for the 
storage device on the two different nodes.   Assuming the major number 
is the same on both systems...is this something that should work?

Any guidance much appreciated - thanks!  I guess this is more of a ZFS 
question..

- Neil

Reply via email to