Well then this is probably the wrong list to be hounding
I am looking for something like
http://blog.wpkg.org/2007/10/26/stale-nfs-file-handle/
Where when fileserver A dies, fileserver B can come up, grab the same
IP address via some mechanism(in this case I am using sun cluster) and
keep on
asa wrote:
Well then this is probably the wrong list to be hounding
I am looking for something like
http://blog.wpkg.org/2007/10/26/stale-nfs-file-handle/
Where when fileserver A dies, fileserver B can come up, grab the same
IP address via some mechanism(in this case I am using sun
I am rolling my own replication using zfs send|recv through the
cluster agent framework and a custom HA shared local storage set of
scripts(similar to http://www.posix.brte.com.br/blog/?p=75 but
without avs). I am not using zfs off of shared storage in the
supported way. So this is a bit
On Nov 10, 2007, at 23:16, Carson Gaspar wrote:
Mattias Pantzare wrote:
As the fsid is created when the file system is created it will be the
same when you mount it on a different NFS server. Why change it?
Or are you trying to match two different file systems? Then you also
have to match
asa wrote:
I would like for all my NFS clients to hang during the failover, then
pick up trucking on this new filesystem, perhaps obviously failing
their writes back to the apps which are doing the writing. Naive?
The OpenSolaris NFS client does this already - has done since IIRC
around
Hello all. I am working on an NFS failover scenario between two
servers. I am getting the stale file handle errors on my (linux)
client which point to there being a mismatch in the fsid's of my two
filesystems when the failover occurs.
I understand that the fsid_guid attribute which is then
2007/11/10, asa [EMAIL PROTECTED]:
Hello all. I am working on an NFS failover scenario between two
servers. I am getting the stale file handle errors on my (linux)
client which point to there being a mismatch in the fsid's of my two
filesystems when the failover occurs.
I understand that the
On Nov 10, 2007, at 3:49 PM, Mattias Pantzare wrote:
2007/11/10, asa [EMAIL PROTECTED]:
Hello all. I am working on an NFS failover scenario between two
servers. I am getting the stale file handle errors on my (linux)
client which point to there being a mismatch in the fsid's of my two
Mattias Pantzare wrote:
As the fsid is created when the file system is created it will be the
same when you mount it on a different NFS server. Why change it?
Or are you trying to match two different file systems? Then you also
have to match all inode-numbers on your files. That is not
