I prefer black tea (and yet all my undefined behavior end up in kernel panic)
Or just don’t mount criss-crossed paths 
Found this:
The Engine mounts binds and volumes read-write unless readonly option is given when mounting the bind or volume. Note that setting readonly for a bind-mount does not make its submounts readonly on the current Linux implementation. See also bind-nonrecursive.
- true or 1 or no value: Mounts the bind or volume read-only.
- false or 0: Mounts the bind or volume read-write.
It’s talking about bind mount so I’m not sure. If this is valid also for volumes then I’m just redundant in declaring the sub dirs as read/write.
Anyway tomorrow I will try removing the read only flag and try to reboot.
Thank you in the meantime!!
About this post, i forgot to ask what happens if you reboot the machine?
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.