We're running 2 machine cluster in development environment just to figure out possible issues with RedHat cluster suite and OpenVZ technology.
Right now we've hit 2 issues.
The first one is using simfs for OpenVZ CT over GFS2 with quota enabled for CT leads us to inconsistent and incorrect disk usage values in quota file and a result CT hits quota and system denies any write attempts to CT. Reinitializing (stop CT, removing quota, start CT) solves issue only for a moment.
Thus we decided to try ploop over GFS2. And thus we hit the second problem:
[root@dev ~]# vzctl create 102 --ostemplate centos-6-x86_64-default --hostname test3 --layout ploop --diskspace 15G
Creating image: /vz/private/102.tmp/root.hdd/root.hdd size=15728640K
Creating delta /vz/private/102.tmp/root.hdd/root.hdd bs=2048 size=31457280 sectors
Storing /gfs2/vz/private/102.tmp/root.hdd/DiskDescriptor.xml
Adding delta dev=/dev/ploop0 img=/gfs2/vz/private/102.tmp/root.hdd/root.hdd (rw)
Error in add_delta (ploop.c:1008): Can't add image /gfs2/vz/private/102.tmp/root.hdd/root.hdd: unsupported underlying filesystem
Failed to create image: Error in add_delta (ploop.c:1008): Can't add image /gfs2/vz/private/102.tmp/root.hdd/root.hdd: unsupported underlying filesystem [3]
Creation of container private area failed
[root@dev ~]#
And so the question is, does anybody have ever succesfully deployed OpenVZ CT over GFS2 including quota support ?
Running following OpenVZ kernel and utils:
Linux dev 2.6.32-042stab057.1 #1 SMP Fri Jun 22 02:17:07 MSD 2012 x86_64 x86_64 x86_64 GNU/Linux
vzkernel-2.6.32-042stab057.1.x86_64
ploop-lib-1.4-1.x86_64
ploop-1.4-1.x86_64
vzctl-lib-3.3-1.x86_64
vzctl-3.3-1.x86_64
Thanks in advance.
[Updated on: Mon, 24 September 2012 08:08]
Report message to a moderator
OpenVZ Forum
Members
Search
Help
Register
Login
Home
