[Error] Restoring Container fails with: extracting archive - error at entry "aquota.group": failed to set file attributes: EPERM: Operation not permit

[rickyo]

Hi,

I'm trying to restore an LXC backup-archive and get the following error message, is there a way to go around it?

Logical volume "vm-198-disk-0" created.
mke2fs 1.44.5 (15-Dec-2018)
Discarding device blocks:     4096/52428801052672/52428801576960/52428802101248/52428802625536/52428803149824/52428803674112/52428804198400/52428804722688/5242880               done                           
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: 5b7a29c9-a7b0-4c50-97f9-9ea7d556897e
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000

Allocating group tables:   0/160       done                           
Writing inode tables:   0/160       done                           
Creating journal (32768 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information:   0/160       done

Error: error extracting archive - error at entry "aquota.group": failed to set file attributes: EPERM: Operation not permitted
  Logical volume "vm-198-disk-0" successfully removed
TASK ERROR: unable to restore CT 198 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client restore '--crypt-mode=none' ct/198/2020-10-26T00:10:24Z root.pxar /var/lib/lxc/198/rootfs --allow-existing-dirs --repository brosoft@pbs@172.16.0.7:PROX_BACKUP_SERVER' failed: exit code 255

Here is the configuration:

arch: amd64
cores: 2
hostname: blueonyx-5209-test-2018
memory: 2048
nameserver: 10.0.0.17
net0: name=eth0,bridge=vmbr1,gw=10.0.0.1,hwaddr=76:42:B7:68:61:5F,ip=10.0.0.224/24,tag=1,type=veth
ostype: centos
rootfs: PROX-LXC:198/vm-198-disk-1.raw,quota=1,size=20G
searchdomain: brosoft.net
swap: 2048

Thanks in advance,

Rickard

 

[wolfgang]

Hi,

I guess you restore the lxc container to a storage that does not support "aquota.group".

 

[rickyo]

Hi,

I guess you restore the lxc container to a storage that does not support "aquota.group".

I suppose LVM sohuld suppoort quota as I run around 50 other machines using it on the same storage.
But, yes, some of these older machines was created on NFS and even old openvz containers just converted to LXC.

I will try to restore the machine to the NFS-storage and then turn off quota, make a new backup, restore to LVM and then turn quota on again.

I'll get back here to report.

Best regards,
Rickard

 

[rickyo]

I suppose LVM sohuld suppoort quota as I run around 50 other machines using it on the same storage.
But, yes, some of these older machines was created on NFS and even old openvz containers just converted to LXC.

I will try to restore the machine to the NFS-storage and then turn off quota, make a new backup, restore to LVM and then turn quota on again.

I'll get back here to report.

Best regards,
Rickard

Ok, tried it on the original storage, doesn't work either.
Something has happened to the container.
Is there a way to turn of quota/aquota.group during restore?

Best regards,
Rickard

 

[wolfgang]

You must extract the "etc/vzdump/pct.conf" and edit it then you can put it back to this path.
the format is tar

 

[rickyo]

You must extract the "etc/vzdump/pct.conf" and edit it then you can put it back to this path.
the format is tar

Hmmm, the backup is on a PBS?

I really don't know what to do...

 

[rickyo]

You must extract the "etc/vzdump/pct.conf" and edit it then you can put it back to this path.
the format is tar

Actually, the problem started while moving storage from NFS to LVM (iscsi).
All VMs moved nicely and most LXC did as well but I have some which won't move.

Here's an example of what my LXC looked like while trying to move the storage before trying the backup-model:


Logical volume "vm-188-disk-0" created.
mke2fs 1.44.5 (15-Dec-2018)
Discarding device blocks: 4096/52428801576960/52428802101248/52428802625536/52428803149824/52428803674112/52428804198400/52428804722688/5242880 done
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: fbdf07ee-b447-4c8c-9dee-efb87d55124b
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: 0/160 done
Writing inode tables: 0/160 done
Creating journal (32768 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/160 done

mount: /var/lib/lxc/188/.copy-volume-2: cannot mount /dev/loop0 read-only.
Specified filename /var/lib/lxc/188/.copy-volume-1 does not exist.
Logical volume "vm-188-disk-0" successfully removed
TASK ERROR: command 'mount -o ro /dev/loop0 /var/lib/lxc/188/.copy-volume-2//' failed: exit code 32