On Tue, 2009-07-14 at 18:33 -0400, Erez Zadok wrote: > How would the client detect that the server broke the promise? In theory, > your client may never know b/c it'll never send the server any > state-changing ops (e.g., creat, write, unlink). One really ugly idea might > be for the client to try and create a dummy .nfsXXXXXX file on the server, > and if that succeds, or the error returned isn't EROFS, the client can guess > that the server's misbhaving. That still doesn't guarantee anything: cat /etc/exports /export 10.0.0.0/24(ro,sync) 10.0.1.1(rw,sync) /export/home 10.0.0.0/24(sec=krb5i:krb5p,rw,sec=sys:krb5,ro) Both of the above are liable to return EROFS to some clients, but not others... NFSv4.1 directory delegations can do the job of notifying you if the directory contents change, but what should your unionfs do when it gets told that this is the case? Cheers Trond -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
