Hi,
we just moved a 2-node proxmox 1.9 to a 3-node proxmox 2.1 cluster - and things look really pretty. Currently, we only see an oddity which we do not really understand: migration of containers do not work - unless the container's config manually is modified with the line
DISK_QUOTA=no
Otherwise, migration alwas tries to call "vzdqdump", which fails because of "Can't open quota file". OpenVZ file system is not extn, but xfs; i guess vzquota still does not support xfs.
However, DISK_QUOTA is set to "no" in /etc/vz/vz.conf - which does not seem to help.
In OpenVZMigrate.pm i can see that vzdqdump should only be called when "DISK_QUOTA" is != 0:
But this thing seems to read the container's config - and there is no "DISK_QUOTA" parameter at all, if not added manually.
Of course, GUI says "user quota disabled", seems to relate to "QUOTAUGIDLIMIT"...
Are we doing something wrong, or is this a little flaw in the migration's code?
we just moved a 2-node proxmox 1.9 to a 3-node proxmox 2.1 cluster - and things look really pretty. Currently, we only see an oddity which we do not really understand: migration of containers do not work - unless the container's config manually is modified with the line
DISK_QUOTA=no
Otherwise, migration alwas tries to call "vzdqdump", which fails because of "Can't open quota file". OpenVZ file system is not extn, but xfs; i guess vzquota still does not support xfs.
However, DISK_QUOTA is set to "no" in /etc/vz/vz.conf - which does not seem to help.
In OpenVZMigrate.pm i can see that vzdqdump should only be called when "DISK_QUOTA" is != 0:
Code:
if (!defined($disk_quota) || ($disk_quota != 0)) {
...
$cmd = "vzdqdump $vmid -U -G -T > " . PVE::Tools::shellquote($self->{quotadumpfile});
But this thing seems to read the container's config - and there is no "DISK_QUOTA" parameter at all, if not added manually.
Of course, GUI says "user quota disabled", seems to relate to "QUOTAUGIDLIMIT"...
Are we doing something wrong, or is this a little flaw in the migration's code?