Timeline for umount: device is busy. Why?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 26, 2024 at 21:16 | comment | added | u_Ltd. | @bparker I attached the loop again with kpartx -av, then detached it with kpartx -d, then it was gone. | |
| Oct 10, 2021 at 19:26 | comment | added | bparker | I also had a stale loop0, but losetup -d /dev/loop0 would NOT actually detach it. running -a still showed it there; never got it to go away. | |
| Sep 13, 2019 at 11:53 | comment | added | P.Péter | +1 for mentioning swap files, they do block unmounting, and are pretty much undetectable if you are not checking them directly. | |
| Apr 13, 2017 at 12:36 | history | edited | CommunityBot | replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/ | |
| S Apr 3, 2014 at 14:38 | history | suggested | n611x007 | CC BY-SA 3.0 | made long script session more readable with slight formatting |
| Apr 3, 2014 at 14:26 | review | Suggested edits | |||
| S Apr 3, 2014 at 14:38 | |||||
| Jun 25, 2012 at 13:39 | comment | added | w00t | All 924 days uptime means is that you need to update your kernel patches :-) | |
| Apr 7, 2012 at 17:52 | history | answered | ZakW | CC BY-SA 3.0 |