Various reasons for the failure of an umount command
Tue, 2013.04.02 - 13:48 — müzso
An umount command usually fails with the following message:
The referenced blog post lists most reasons for an umount to fail. The use of
umount: /mnt/test: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))The referenced blog post lists most reasons for an umount to fail. The use of
lsof and fuser is quite common knowledge. However the use of the -v option with lsof is not. Eg. if you try to umount an NFS exported directory and run lsof and fuser, both will produce nothing. But the umount still fails. If you run fuser with the -v option, it'll point out the culprit, namely the kernel's NFS code holding locks on the given partition (as explained here):# fuser -v -m /mnt/test
USER PID ACCESS COMMAND
/mnt/test: root kernel mount /mnt/test
All of my own contents here (if not noted otherwise) are licensed under the
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License. My posts reflect my personal opinion and shall not be associated with any of my employers.
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License. My posts reflect my personal opinion and shall not be associated with any of my employers.
Recent comments
2 years 31 weeks ago
4 years 1 week ago
4 years 1 week ago
4 years 3 weeks ago
4 years 4 weeks ago
4 years 10 weeks ago
4 years 10 weeks ago
4 years 11 weeks ago
4 years 11 weeks ago
4 years 11 weeks ago