Nicolas Williams wrote: >> The files need to be created, in order to emulate the expected behaviour >> where open files remain accessible after unlinking, with the file being >> removed only on "last close". An NFSv3 server cannot support this, since >> there is no open/close in v3, and it's hard in v4, so we handle this on >> the client with the .nfsXXXX rename mechanism. > > NFSv4 ought to be able to do avoid this,
The problem with v4 is how to handle server reboot: if the server reboots after the file has been deleted, but whilst it's still open, we need some trickery in various places to be able to recover from that. In the absence of the trickery required in v4 server and backend filesystem, the v4 client needs to do the rename as per the v3 client. cheers, c.
