Hello all, Some way to workaround the filehandle issue with a send/receive ZFS procedure? In the ZFS begining, i did a conversation with some of the devel guys, and did ask about how ZFS would treat the NFS filehandle.. IIRC, the answere was: "No problem, the NFS filehandle will not depend on the disk/path/creation... like ufs or other filesystems". So i thought (wrong maybe ;), all informations required to preserve the FH consistency would be on the filesystem itself. I did some tests with send/receive a filesystem from one node to another, changing the IP from one node to the other, and got the FH issue (stale), from a GNU/Linux client. Any chance to have a working scenario like this, or for non-shared discs i need to have many pools, and in the case i want to migrate (portions of) the NFS services, i need to hot-swap discs (export/import the pool on the other host)? Thanks. -- This message posted from opensolaris.org
Hi Marcelo,> I did some tests with send/receive a filesystem from one node to another, > changing the IP from one node to the other, and got the FH issue (stale), from a GNU/Linux client.How are you replicating the filesystems? zfs send | zfs recv ? This method will preserve the inodes but you will end up with two different filesystem ids. The (solaris kernel-) NFS server uses various values to create a filehandle, one of them is the fsid: Checkout http://blogs.sun.com/peteh/entry/understanding_snoop_1m_nfsv3_file Changing the fsid of a ZFS-Filesystem is, as far as i know, not possible/supported (and would be scary anyway..) There also seems to be no way to tell the nfsd to not use the fsid (linux knfsd has a fsid option, this would solve your problem... Any chance that Sun will implement this?) I was also trying to build a Cheapo-HA-NFS-Cluster using zfs send|recv some weeks ago and ended up with a patched version of unfs3d. unfs3d is not as fast (and reliable) as nfsd but it has one big advantage: It works ;-) . Regards, Adrian
Hello Adrian, Thanks, i was using send/receive (that?s why i did put it on subject ;), and i did like to know if ZFS could have some solution for that as i said before. The send/receive is not an "exact" copy of the filesystem (creation time, fsid, etc) are different. So, the FH using that for composition, the ZFS has the same problem like any other filesystem (stale issue). It was just a guess, as i was trying the "same" filesystem, maybe the references inside it would remain the same, and Solaris/ZFS could not be using the "things" that cause this issue... ps.: I woul like to find my chat with the ZFS engineer. I should have misunderstood him. Thanks again! -- This message posted from opensolaris.org