Something in the recent VFS churn appears to have broken NFS sillyrename. Currently, when I try to unlink() a file that is being held open by another process, I do indeed see that file getting renamed to a .nfsxxxxxxx file, but when the file is closed, the .nfsxxxxx file sticks around until I unlink() it again. I'll have a look tomorrow at what is going wrong, but I figured I'd ask on the list in case someone has a suspect... 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-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
