Timeline for umount: device is busy. Why?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 27, 2017 at 16:34 | comment | added | dpw | I'm not sure of the what the technical difference is, but while investigating a stale NFS mount, lsof /path yielded nothing whereas lsof | grep /path showed me the process that was holding open files and preventing me from unmounting the volume. | |
| Jun 16, 2011 at 10:10 | comment | added | Ole Tange | Like I said: lsof /path looks at the path only. It does not look at every single file. It is often much faster than lsof | grep /path (in my unscientific test it was 20 times faster YMMV) since it does not look at all open files but only the files for that path. | |
| Jun 15, 2011 at 12:02 | comment | added | Caleb | I didn't say lsof /path, I said lsof | grep '/path'. The difference is that lsof with no arguments shows all open files using some sort of cache table, and grep is very fast at searching through it. The things you tried with lsof make it scan through the file system which takes a long time. | |
| Jun 15, 2011 at 11:58 | comment | added | Ole Tange | lsof /path looks through the path only. | |
| Jun 15, 2011 at 11:52 | history | answered | Caleb | CC BY-SA 3.0 |