Well, I agree in theory but...
Assuming you're using Linux at some point you will come across those words that make even the most hardened systems/storage admin tremble.
nfs-kernel-server.
I swear to fucking god they designed that thing just to mess with us. Anyone recognise this?
You need to delete this directory because $USER doesn't work here any more.
# umount /pool/home/$USER
umount: /pool/home/$USER: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
cannot unmount '/pool/home/$USER': umount failed
Wait... mounted? No they bloody don't. $USER has had their account deactivated. They've left the building. Their machine has been returned to the pool. No one other than the IT team could have mounted their share anyway - what gives?
Oh, wait, they turned the machine off at the wall didn't they. Well, now we're screwed, becuase nfs-fucking-kernel-server is going to sit there and await an unmount from the client and the only way to stop it is to restart the daemon - kicking everyone who actually IS using it.
(Honestly tho - if anyone has any ideas how the HELL you kick a user from a Linux NFS server in order to cause the kernel to release its lock on an exported filesystem, this is a bane-of-my-life type problem)
Biting the hand that feeds IT
