Subject: Re: vnamespace mount -o remount,ro does not make it read-only
From: Christian Jaeger <chrjae@gmail.com>
Date: Thu, 1 Dec 2011 22:20:18 -0500

Just when I finished the above, I had an idea:

(Mis-using the existing dir /var/lib/vservers/build64/home/chris/GIT
just because I'm too lazy to create a directory somewhere else)

tn:/etc/vservers# vnamespace -e t3 mount --bind ~chris/GIT/
/var/lib/vservers/build64/home/chris/GIT
tn:/etc/vservers# vnamespace -e t3 mount -o remount,ro
/var/lib/vservers/build64/home/chris/GIT
tn:/etc/vservers# vnamespace -e t3 mount --bind
/var/lib/vservers/build64/home/chris/GIT
/var/lib/vservers/t3/home/chris/GIT
chris@t3:~$ touch GIT/feh
touch: cannot touch `GIT/feh': Read-only file system

*good* (this also avoids the time gap with read-write access from the guest)

But I'd still like to know why the remount,ro had no effect on the
guest in the first case.

Christian.