Hm, well I removed the scripts, now I get the error: repquota: Can't stat() mounted device /dev/ploop50951p1: No such file or directory
I don't know if this is related at all, it kinda started after a recent update to the latest kernel 2.6.32-042stab102.9 Now if I go into any container on this hardware node, the /dev/ploopXXX devices listed in /proc/mount doesn't exist. For example: root@vps2202 [~]# cat /proc/mounts /dev/ploop50951p1 / ext4 rw,relatime,barrier=1,stripe=256,data=ordered,balloon_ino=12,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0 /dev/simfs /backup simfs rw,relatime 0 0 proc /proc proc rw,relatime 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /dev tmpfs rw,relatime,size=7992992k,nr_inodes=1998248 0 0 none /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 root@vps2202 [~]# ll /dev/ploop50951p1 /bin/ls: /dev/ploop50951p1: No such file or directory There are quite a few /dev/ploop* devices under /dev, but not the one linked in /proc/mounts. This goes for all containers on this hardware node. Other nodes not yet upgraded to the latest kernel do not have this problem. Any ideas? On Sat, Dec 27, 2014 at 12:31 AM, Kir Kolyshkin <k...@openvz.org> wrote: > > On 12/26/2014 09:46 AM, Scott Dowdle wrote: > >> Greetings, >> >> ----- Original Message ----- >> >>> I'm still waiting to hear what is the PROPER way of discarding this >>> script. Just deleting the base file will cause a large number of >>> symlinks to become orphans. >>> >> 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. >> > > No, the script (and its appropriate symlinks) is (re)created on every > start (actually mount) > of a simfs-based container. It is a conversion process that should get rid > of it, unfortunately > vzctl doesn't do it currently, so has to be done manually. Feel free to > file a bug for vzctl. > > Kir. > > _______________________________________________ > 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
