I tried just removing it, does not seem to fix anything. Need to do anything else? Remount, restart, anything?
On Thu, Dec 12, 2013 at 11:43 AM, Rene C. <ope...@dokbua.com> wrote: > Ok thanks. Just remove it, nothing else? Need to restart the > container or anything? > > On Thu, Dec 12, 2013 at 10:02 AM, Kir Kolyshkin <k...@openvz.org> wrote: >> On 12/11/2013 06:28 PM, Rene C. wrote: >>> >>> I just noticed there is a contaner on one of our hardware nodes that >>> appears to have been changed to ploop, but the filesystem is still >>> simfs: >>> >>> # vzctl exec 1703 df -h >>> Filesystem Size Used Avail Use% Mounted on >>> /dev/simfs 99G 65G 29G 70% / >>> none 1.0G 4.0K 1.0G 1% /dev >>> # vzctl convert 1703 >>> CT is already on ploop >>> >>> >>> All other containers use a /dev/ploopXXXX device. >>> >>> Is this a problem? Should it be fixed? How? >> >> >> I guess this is caused by a record in CT's /etc/mtab. This should be >> harmful. >> If you want to fix it, just remove CT's /etc/mtab >> _______________________________________________ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
