A couple have the ploop device and a couple don't*
> Devon B. <mailto:devo...@virtualcomplete.com> > Wednesday, January 21, 2015 11:52 AM > I looked at a few more containers. A couple have the ploop device and > a couple do. I'm not sure why. Most that do have the ploop devices > have a bunch of stale ones. For instance: > > # vzctl exec #### ls -l "/dev/ploop*" > b-----x--- 1 root root 182, 300625 Jan 18 22:57 /dev/ploop18789p1 > b-----x--- 1 root root 182, 355073 Jan 18 22:57 /dev/ploop22192p1 > b-----x--- 1 root root 182, 371265 Jan 18 22:57 /dev/ploop23204p1 > b-----x--- 1 root root 182, 428529 Jan 18 22:57 /dev/ploop26783p1 > b-----x--- 1 root root 182, 525073 Jan 18 22:57 /dev/ploop32817p1 > b-----x--- 1 root root 182, 655857 Jan 18 22:57 /dev/ploop40991p1 > b-----x--- 1 root root 182, 727537 Jan 18 22:57 /dev/ploop45471p1 > brw-rw---T 1 root disk 182, 749697 Jan 18 22:57 /dev/ploop46856p1 > b-----x--- 1 root root 182, 773185 Jan 18 22:57 /dev/ploop48324p1 > b-----x--- 1 root root 182, 864529 Jan 18 22:57 /dev/ploop54033p1 > b-----x--- 1 root root 182, 897201 Jan 18 22:57 /dev/ploop56075p1 > > The active one is pretty obvious (/dev/ploop46856p1). It doesn't > seem to be specific to node or kernel, the containers are split on the > same system. > > Have you filed a bug report? > > Rene C. <mailto:ope...@dokbua.com> > Wednesday, January 21, 2015 11:27 AM > The reason I became aware of the problem was that a cpanel servers > started sending this message every morning: > > repquota: Can't stat() mounted device /dev/ploop50951p1: No such file > or directory > > All containers on another hardware node and several on this have the > devices working correctly within the containers. > > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > Devon B. <mailto:devo...@virtualcomplete.com> > Wednesday, January 21, 2015 11:11 AM > I can't speak as to how to address the issue, but why do you consider > it messed up? I logged in to a few nodes and saw the same thing on > all of them and I don't remember this being any different in the > past. The ploop device only exists outside of the container (when > mounted). Inside the container is just a reference, no actual device > exists. > > I don't know enough about the original issue, what are you trying to > accomplish with the ploop device inside the container? > > > Rene C. <mailto:ope...@dokbua.com> > Wednesday, January 21, 2015 6:47 AM > I've gone through all containers and actually some of them work > correctly, only some are messed up like this. > > Take for example this one: > > [root@server22 ~]# vzctl restart 2201 > Restarting container > Stopping container ... > Container was stopped > Unmounting file system at /vz/root/2201 > Unmounting device /dev/ploop27939 > Container is unmounted > Starting container... > Opening delta /vz/private/2201/root.hdd/root.hdd > Adding delta dev=/dev/ploop27939 > img=/vz/private/2201/root.hdd/root.hdd (ro) > Adding delta dev=/dev/ploop27939 > img=/vz/private/2201/root.hdd/root.hdd.{7a09b730-f2d6-4b21-b856-0bd6ca420a6e} > (rw) > Mounting /dev/ploop27939p1 at /vz/root/2201 fstype=ext4 > data='balloon_ino=12,' > Container is mounted > Adding IP address(es): (redacted) > Setting CPU limit: 400 > Setting CPU units: 50 > Setting CPUs: 4 > Container start in progress... > > So apparently the ploop device should be /dev/ploop/27939. Everything > seems to work, inside the container this device is referred by > /proc/mounts > > [root@server22 ~]# vzctl exec 2201 cat /proc/mounts > /dev/ploop27939p1 / 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 tmpfs rw,relatime,mode=755 0 0 > none /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 > none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 > > But the device is actually missing: > > [root@server22 ~]# vzctl exec 2201 ls -l /dev/ploop27939p1 > ls: /dev/ploop27939p1: No such file or directory > > In fact, there doesn't seem to be ANY /dev/ploop devices in this container > > [root@server22 ~]# vzctl exec 2201 ls -l /dev/ploop* > ls: /dev/ploop18940: No such file or directory > ls: /dev/ploop18940p1: No such file or directory > ls: /dev/ploop26517: No such file or directory > ls: /dev/ploop26517p1: No such file or directory > ls: /dev/ploop27379: No such file or directory > ls: /dev/ploop27379p1: No such file or directory > ls: /dev/ploop27939: No such file or directory > ls: /dev/ploop27939p1: No such file or directory > ls: /dev/ploop50951: No such file or directory > ls: /dev/ploop50951p1: No such file or directory > ls: /dev/ploop52860: No such file or directory > ls: /dev/ploop52860p1: No such file or directory > ls: /dev/ploop58415: No such file or directory > ls: /dev/ploop58415p1: No such file or directory > > Why does it shows devices when there are none present? Obviously > something is messed up, how can we fix this? > > > > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > Rene C. <mailto:ope...@dokbua.com> > Tuesday, January 20, 2015 12:04 PM > > No takers? > > > > _______________________________________________ > 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