This question is old and I'm not sure if the circumstances I endured are similar or completely different. However, I did find the solution to my issue with the same symptom.
I was trying to clean a directory from build cruft via rm -rf build/tmp/path
and a file deep in the tree named .nfs000*
was throwing the "Device or resource is busy" error.
My problem was multi-faceted. The first element was the use of roaming home directories at the office. The second, was docker and the use of containers. Finally, vim and editing a file. While in the container, I was abruptly disconnected from my terminal which killed the shell and the vim program I had running, but it did not kill the container. However, because vim was dead no process did have that file open (but the container did). Finally, it wasn't called the usual .something.swp
as vim temp file would because an attempt to delete it had taken place. That's when NFS stepped in to "save the day." Killing the containe solved the problem.
I don't know if this is what the OP had back then. I offer this only that, when someone else stumbles onto this, perhaps this will inspire you to think indirectly about the cause. This link actually provided me the inspiration for the problem. After cat
ing the file, I found it was a VIM tmp file.