As a workaround instead of stopping and restarting you might want to use vmount
on the affected vservers:
# vmount foo -- -a
You will get some error messages for all already correctly mounted filesystems,
but you can enter your vserver again.
Running
###
for vserver in `vserver-stat | tail -n +2 | awk '{print $8}'`; do
vmount $vserver -- -a
done
###
will fix all your vservers - broken or not (and give some more error messages).
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c503e11.1050...@dimdi.de
