Timeline for mv: cannot move "home" to "home-old": Device or resource busy
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2017 at 7:51 | history | edited | sourcejedi | CC BY-SA 3.0 | added 302 characters in body |
| Mar 8, 2017 at 16:39 | comment | added | sourcejedi | (because /lib/systemd/system/NetworkManager.service uses ProtectHome, at least on the systems we're looking at) | |
| Mar 8, 2017 at 16:22 | vote | accept | TheAmigo | ||
| Mar 8, 2017 at 16:22 | comment | added | TheAmigo | I found another "broken" machine and your grep command indeed points the finger at NetworkManager. So my "stop NM, rename, restart NM" works, but your grep of mountinfo is what find the culprit. | |
| Mar 8, 2017 at 15:14 | history | edited | sourcejedi | CC BY-SA 3.0 | added 7 characters in body |
| Mar 8, 2017 at 15:05 | history | edited | sourcejedi | CC BY-SA 3.0 | added 7 characters in body |
| Mar 8, 2017 at 15:00 | comment | added | sourcejedi | Does that mean you used commands along the lines I suggested? Because "never" is a very strong assertion, my commands wouldn't demonstrate that. I've added a command at the start which would be simpler (and hopefully functional :), and a second speculation on why this might happen based on the result on my system. | |
| Mar 8, 2017 at 14:55 | history | edited | sourcejedi | CC BY-SA 3.0 | added 659 characters in body |
| Mar 8, 2017 at 14:14 | comment | added | TheAmigo | /home has never been a mount in any namespace. | |
| Mar 7, 2017 at 22:37 | history | answered | sourcejedi | CC BY-SA 3.0 |