On Mon, 18 Oct 2010 11:01:38 -0400 Jeff Layton <jlayton@xxxxxxxxxx> wrote: > On Mon, 18 Oct 2010 15:53:44 +0100 > ClÃudio Martins <ctpm@xxxxxxxxxx> wrote: > > > > > > > So, theoretically, could one modify the code to selectively disable > > > silly rename on a client, when it knows it is talking v4 with the > > > server? > > > > > > > BTW, to clarify, I'm assuming a scenario where the server is > > configured to talk v4 only, which I suspect should be common, at least > > when you're relying on v4 kerberos security. > > > > Sadly, no... > > The server does generally hold the file open as long as the client has > the file open. So, you could delete the file while nfsd has it open and > everything would probably still work. > > Suppose though that the server crashes and reboots. When it comes back > up, fsck figures out that the file has been unlinked and frees the > blocks on the disk. Now you can't reclaim the state on the open file. > > We're pretty much stuck with silly-renaming even for v4. > Jeff, Thank you for the explanation, you make a good point. Best regards ClÃudio -- 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
