Timeline for Cannot umount /dev bind-mount
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 10, 2022 at 8:56 | comment | added | Bruno |
looking again at documentation, I don't see how using a slave mount could solve the issue, because the binded mount itself could not be unmounted. It is not a question of propagating anything to the "master" (/dev). Imagine that something makes this binded device busy for some reason (like a magic process doing a cd in the mount dir), being a slave or not will not change anything. Or do I miss something ?
|
|
| Mar 9, 2022 at 13:13 | comment | added | MC68020 | @Bruno : (cf comment #1) These (bind and slave) are two different things. You do need to bind, then, unless accepting default, specify the type of the mount (shared / slave / private mount / unbindable) I separated the two steps because that is what I do, it is possible that the two actions can be mixed into a single mount instruction, I did not check. | |
| Mar 9, 2022 at 11:46 | comment | added | Bruno |
My main issue here is in fact that I cannot reproduce the problem (it happened once only, and I used the script quite often - 50-100 times ?). I think I will have to close this issue later today if I cannot get more information on what could have happened. Also, for these kind of devices, maybe I could simply use -t umount option if the first umount fails, I don't see any risk on this kind of filesystem.
|
|
| Mar 9, 2022 at 11:31 | comment | added | Bruno |
Thanks, I did read a little yesterday about these options when looking for my error; I will try to adapt my script when I understand the basics, starting with the difference between bind and slave (I did not know about slave mount before yesterday).
|
|
| Mar 8, 2022 at 22:17 | history | answered | MC68020 | CC BY-SA 4.0 |