[Users] simfs with ploop?

[Kir Kolyshkin]

On 12/17/2013 12:27 AM, Rene C. wrote:
> Sure ....
>
> # ls -l /vza1/private/1703
> total 16
> drwxr-xr-x 2 root root 4096 Dec 15 04:10 dump
> drwx------ 3 root root 4096 Dec 15 04:10 root.hdd
> -rw-r--r-- 1 root root  443 Dec 15 04:09 Snapshots.xml
> -rw-r--r-- 1 root root   37 Dec 15 03:06 vzpbackup_snapshot
> # vzlist -o layout 1703
> LAYOUT
> ploop
> #
>
> Surely deleting the mount table isn't healthy, isn't it needed by something?

This is how it should look like:

[host] # vzctl enter 1018
entered into CT 1018
[CT1018] # ls -l /etc/mtab
lrwxrwxrwx 1 root root 12 Nov  7 21:20 /etc/mtab -> /proc/mounts

And /proc/mounts is showing info from the kernel which can't be wrong:

[CT1018]# cat /proc/mounts
/dev/ploop51540p1 / ext4 
rw,relatime,barrier=1,data=ordered,balloon_ino=12 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /dev devtmpfs rw,relatime,mode=755 0 0
none /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
none /dev/shm tmpfs rw,relatime 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0


>
> On Tue, Dec 17, 2013 at 9:41 AM, Kir Kolyshkin <kir at openvz.org> wrote:
>> On 12/16/2013 04:51 PM, Rene C. wrote:
>>> I tried just removing it, does not seem to fix anything. Need to do
>>> anything else? Remount, restart, anything?
>>
>> Would be great if you can copy-paste some output from the terminal,
>> otherwise it's more complicated to debug.
>>
>> Maybe your CT was not really converted.
>>
>> Please show output of
>>
>> ls -l /vz/private/1703/
>> vzlist -o layout 1703
>>
>>
>> On Thu, Dec 12, 2013 at 11:43 AM, Rene C. <openvz at 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 <kir at 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 at openvz.org
>>>>> https://lists.openvz.org/mailman/listinfo/users
>>> _______________________________________________
>>> Users mailing list
>>> Users at openvz.org
>>> https://lists.openvz.org/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users at openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://lists.openvz.org/mailman/listinfo/users