Hello everyone,
I've been using linux acls (getfacl/setfacl) inside a container for a while now. While moving things around, I've noticed that the current implementation of vzmigrate in the latest release (proxmox 1.9 as of writing) doesn't use the preserve acl flag for the rsync call that performs underneath. Just by adding the "--acls" flag in the RSYNC_OPTIONS variable, makes the migration process keep the acls defined in the extended attributes of the filesystem (given that both the source and destination machines support extended attributes within their filesystems). Patch:
From:
To:
I tested the patch in a production environment with success. I tried writing to the OpenVZ guys as well, but their forum posting settings seem awkward.
I've been using linux acls (getfacl/setfacl) inside a container for a while now. While moving things around, I've noticed that the current implementation of vzmigrate in the latest release (proxmox 1.9 as of writing) doesn't use the preserve acl flag for the rsync call that performs underneath. Just by adding the "--acls" flag in the RSYNC_OPTIONS variable, makes the migration process keep the acls defined in the extended attributes of the filesystem (given that both the source and destination machines support extended attributes within their filesystems). Patch:
From:
Code:
RSYNC_OPTIONS="-aH --delete --numeric-ids"
Code:
RSYNC_OPTIONS="-aH --delete --numeric-ids --acls"I tested the patch in a production environment with success. I tried writing to the OpenVZ guys as well, but their forum posting settings seem awkward.
