<div dir="ltr">I've gone through all containers and actually some of them work correctly, only some are messed up like this.<div><br></div><div>Take for example this one:</div><div><br></div><div><div><font face="monospace, monospace">[root@server22 ~]# vzctl restart 2201</font></div><div><font face="monospace, monospace">Restarting container</font></div><div><font face="monospace, monospace">Stopping container ...</font></div><div><font face="monospace, monospace">Container was stopped</font></div><div><font face="monospace, monospace">Unmounting file system at /vz/root/2201</font></div><div><font face="monospace, monospace">Unmounting device /dev/ploop27939</font></div><div><font face="monospace, monospace">Container is unmounted</font></div><div><font face="monospace, monospace">Starting container...</font></div><div><font face="monospace, monospace">Opening delta /vz/private/2201/root.hdd/root.hdd</font></div><div><font face="monospace, monospace">Adding delta dev=/dev/ploop27939 img=/vz/private/2201/root.hdd/root.hdd (ro)</font></div><div><font face="monospace, monospace">Adding delta dev=/dev/ploop27939 img=/vz/private/2201/root.hdd/root.hdd.{7a09b730-f2d6-4b21-b856-0bd6ca420a6e} (rw)</font></div><div><font face="monospace, monospace">Mounting /dev/ploop27939p1 at /vz/root/2201 fstype=ext4 data='balloon_ino=12,'</font></div><div><font face="monospace, monospace">Container is mounted</font></div><div><font face="monospace, monospace">Adding IP address(es): (redacted)</font></div><div><font face="monospace, monospace">Setting CPU limit: 400</font></div><div><font face="monospace, monospace">Setting CPU units: 50</font></div><div><font face="monospace, monospace">Setting CPUs: 4</font></div><div><font face="monospace, monospace">Container start in progress...</font></div></div><div><br></div><div>So apparently the ploop device should be /dev/ploop/27939. Everything seems to work, inside the container this device is referred by /proc/mounts</div><div><br></div><div><div><font face="monospace, monospace">[root@server22 ~]# vzctl exec 2201 cat /proc/mounts</font></div><div><font face="monospace, monospace">/dev/ploop27939p1 / ext4 rw,relatime,barrier=1,data=ordered,balloon_ino=12 0 0</font></div><div><font face="monospace, monospace">proc /proc proc rw,relatime 0 0</font></div><div><font face="monospace, monospace">sysfs /sys sysfs rw,relatime 0 0</font></div><div><font face="monospace, monospace">none /dev tmpfs rw,relatime,mode=755 0 0</font></div><div><font face="monospace, monospace">none /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0</font></div><div><font face="monospace, monospace">none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0</font></div></div><div><br></div><div>But the device is actually missing:</div><div><br></div><div><div><font face="monospace, monospace">[root@server22 ~]# vzctl exec 2201 ls -l /dev/ploop27939p1</font></div><div><font face="monospace, monospace">ls: /dev/ploop27939p1: No such file or directory</font></div></div><div><br></div><div>In fact, there doesn't seem to be ANY /dev/ploop devices in this container</div><div><br></div><div><div><font face="monospace, monospace">[root@server22 ~]# vzctl exec 2201 ls -l /dev/ploop*</font></div><div><font face="monospace, monospace">ls: /dev/ploop18940: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop18940p1: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop26517: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop26517p1: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop27379: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop27379p1: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop27939: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop27939p1: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop50951: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop50951p1: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop52860: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop52860p1: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop58415: No such file or directory</font></div><div><font face="monospace, monospace">ls: /dev/ploop58415p1: No such file or directory</font></div></div><div><br></div><div>Why does it shows devices when there are none present? Obviously something is messed up, how can we fix this?</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 20, 2015 at 6:04 PM, Rene C. <span dir="ltr"><<a href="mailto:openvz@dokbua.com" target="_blank">openvz@dokbua.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div>No takers?</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 13, 2015 at 6:00 PM, Rene C. <span dir="ltr"><<a href="mailto:openvz@dokbua.com" target="_blank">openvz@dokbua.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hm, well I removed the scripts, now I get the error:<div><br></div><div><span style="font-size:13px">repquota: Can't stat() mounted device /dev/ploop50951p1: No such file or directory</span><br></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">I don't know if this is related at all, it kinda started after a recent update to the latest kernel </span>2.6.32-042stab102.9</div><div><br></div><div>Now if I go into any container on this hardware node, the /dev/ploopXXX devices listed in /proc/mount doesn't exist.</div><div><br></div><div>For example:</div><div><br></div><div><div>root@vps2202 [~]# cat /proc/mounts</div><div>/dev/ploop50951p1 / ext4 rw,relatime,barrier=1,stripe=256,data=ordered,balloon_ino=12,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0</div><div>/dev/simfs /backup simfs rw,relatime 0 0</div><div>proc /proc proc rw,relatime 0 0</div><div>none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0</div><div>sysfs /sys sysfs rw,relatime 0 0</div><div>none /dev tmpfs rw,relatime,size=7992992k,nr_inodes=1998248 0 0</div><div>none /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0</div><div>root@vps2202 [~]# ll /dev/ploop50951p1</div><div>/bin/ls: /dev/ploop50951p1: No such file or directory</div></div><div><br></div><div>There are quite a few /dev/ploop* devices under /dev, but not the one linked in /proc/mounts. <br><br>This goes for all containers on this hardware node. Other nodes not yet upgraded to the latest kernel do not have this problem.</div><div><br>Any ideas?</div><div><br></div><div><br></div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 27, 2014 at 12:31 AM, Kir Kolyshkin <span dir="ltr"><<a href="mailto:kir@openvz.org" target="_blank">kir@openvz.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On 12/26/2014 09:46 AM, Scott Dowdle wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Greetings,<br>
<br>
----- Original Message -----<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm still waiting to hear what is the PROPER way of discarding this<br>
script. Just deleting the base file will cause a large number of<br>
symlinks to become orphans.<br>
</blockquote>
What I understood Kir to say was that the script was created as part of the conversion process and should have been automatically removed (like it was automaically created) after the conversion was complete. Why it wasn't removed I don't know... but you can back up the file somewhere else... and remove it... and if you have problems... you could copy it back. I don't think any of that would be necessary but who knows.<br>
</blockquote>
<br>
No, the script (and its appropriate symlinks) is (re)created on every start (actually mount)<br>
of a simfs-based container. It is a conversion process that should get rid of it, unfortunately<br>
vzctl doesn't do it currently, so has to be done manually. Feel free to file a bug for vzctl.<br>
<br>
Kir.<br>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/<u></u>mailman/listinfo/users</a><br>
</blockquote></div><br></div></div>
</blockquote></div><br></div>
</blockquote></div><br></div>