[SOLVED] LXC Backup fehler wegen ACL

[CH.illig]

Generelles Setup,
Proxmox 7.4 (7.3 basis installation + Updates)
Setup als ZFS via GUI Installer
LXC Container mit debian Template, und nach installiertem Nextcloud (LAMP)


Problem ist das Backup des LXC Containers auf einem Proxmox Backup server bei mir aber das Backup Target ist egal in dem fall.


Backup Fehlermeldung:

Spoiler

vzdump 1010248 1010249 --notes-template '{{guestname}}' --mailnotification failure --storage svdrz120_pbs-dto-xxxxxxxxxxx --mode snapshot --exclude-path /var/lib/php/sessions --node svdrz241 --mailto info@datarun.ch --all 0


1010248: 2023-06-22 09:11:31 INFO: Starting Backup of VM 1010248 (lxc)
1010248: 2023-06-22 09:11:31 INFO: status = running
1010248: 2023-06-22 09:11:31 INFO: CT Name: svimo248.xxxxxxxxxxx.ch
1010248: 2023-06-22 09:11:31 INFO: including mount point rootfs ('/') in backup
1010248: 2023-06-22 09:11:31 INFO: mode failure - some volumes do not support snapshots
1010248: 2023-06-22 09:11:31 INFO: trying 'suspend' mode instead
1010248: 2023-06-22 09:11:31 INFO: backup mode: suspend
1010248: 2023-06-22 09:11:31 INFO: ionice priority: 7
1010248: 2023-06-22 09:11:31 INFO: CT Name: svimo248.xxxxxxxxxxx.ch
1010248: 2023-06-22 09:11:31 INFO: including mount point rootfs ('/') in backup
1010248: 2023-06-22 09:11:31 INFO: starting first sync /proc/2596689/root/ to /var/tmp/vzdumptmp2230708_1010248
1010248: 2023-06-22 09:12:28 ERROR: Backup of VM 1010248 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/var/lib/php/sessions' '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/2596689/root//./ /var/tmp/vzdumptmp2230708_1010248' failed: exit code 23

1010249: 2023-06-22 09:12:28 INFO: Starting Backup of VM 1010249 (qemu)
1010249: 2023-06-22 09:12:28 INFO: status = running
1010249: 2023-06-22 09:12:28 INFO: VM Name: srv249.xxxxxxxxxxx.ch
1010249: 2023-06-22 09:12:28 INFO: include disk 'scsi0' 'ClusterCeph:vm-1010249-disk-1' 50G
1010249: 2023-06-22 09:12:28 INFO: include disk 'scsi1' 'ClusterCeph:vm-1010249-disk-3' 100G
1010249: 2023-06-22 09:12:28 INFO: include disk 'efidisk0' 'ClusterCeph:vm-1010249-disk-0' 1M
1010249: 2023-06-22 09:12:28 INFO: include disk 'tpmstate0' 'ClusterCeph:vm-1010249-disk-2' 4M
1010249: 2023-06-22 09:12:29 INFO: backup mode: snapshot
1010249: 2023-06-22 09:12:29 INFO: ionice priority: 7
1010249: 2023-06-22 09:12:29 INFO: creating Proxmox Backup Server archive 'vm/1010249/2023-06-22T07:12:28Z'
1010249: 2023-06-22 09:12:29 INFO: attaching TPM drive to QEMU for backup
1010249: 2023-06-22 09:12:29 INFO: issuing guest-agent 'fs-freeze' command
1010249: 2023-06-22 09:12:33 INFO: issuing guest-agent 'fs-thaw' command
1010249: 2023-06-22 09:12:34 INFO: started backup task 'ec05eea2-2ce5-45c5-81be-55f63cb87842'
1010249: 2023-06-22 09:12:34 INFO: resuming VM again
1010249: 2023-06-22 09:12:34 INFO: efidisk0: dirty-bitmap status: OK (drive clean)
1010249: 2023-06-22 09:12:34 INFO: scsi0: dirty-bitmap status: OK (1.4 GiB of 50.0 GiB dirty)
1010249: 2023-06-22 09:12:34 INFO: scsi1: dirty-bitmap status: OK (3.4 GiB of 100.0 GiB dirty)
1010249: 2023-06-22 09:12:34 INFO: tpmstate0-backup: dirty-bitmap status: created new
1010249: 2023-06-22 09:12:34 INFO: using fast incremental mode (dirty-bitmap), 4.8 GiB dirty of 150.0 GiB total
1010249: 2023-06-22 09:12:37 INFO: 74% (3.6 GiB of 4.8 GiB) in 3s, read: 1.2 GiB/s, write: 517.3 MiB/s
1010249: 2023-06-22 09:12:40 INFO: 86% (4.1 GiB of 4.8 GiB) in 6s, read: 186.7 MiB/s, write: 182.7 MiB/s
1010249: 2023-06-22 09:12:43 INFO: 94% (4.5 GiB of 4.8 GiB) in 9s, read: 142.7 MiB/s, write: 138.7 MiB/s
1010249: 2023-06-22 09:12:46 INFO: 100% (4.8 GiB of 4.8 GiB) in 12s, read: 81.3 MiB/s, write: 77.3 MiB/s
1010249: 2023-06-22 09:12:46 INFO: Waiting for server to finish backup validation...
1010249: 2023-06-22 09:12:47 INFO: backup is sparse: 2.01 GiB (42%) total zero data
1010249: 2023-06-22 09:12:47 INFO: backup was done incrementally, reused 147.32 GiB (98%)
1010249: 2023-06-22 09:12:47 INFO: transferred 4.75 GiB in 13 seconds (374.5 MiB/s)
1010249: 2023-06-22 09:12:47 INFO: adding notes to backup
1010249: 2023-06-22 09:12:47 INFO: Finished Backup of VM 1010249 (00:00:19)

Abbruch also beim rsync
diesen nachgebaut sieht es in der vm so aus:

Spoiler

rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/var/lib/php/sessions' '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/2596689/root//./ /var/tmp/test
rsync: [generator] set_acl: sys_acl_set_file(var/log/journal, ACL_TYPE_ACCESS): Operation not supported (95)
rsync: [generator] set_acl: sys_acl_set_file(var/log/journal/a1e9a5aac6fa4a8a91d9a1350341542f, ACL_TYPE_ACCESS): Operation not supported (95)
rsync: [generator] set_acl: sys_acl_set_file(var/log/journal/c5b67cb2fb4c49678a4fd62f7e4a2b20, ACL_TYPE_ACCESS): Operation not supported (95)
rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/a1e9a5aac6fa4a8a91d9a1350341542f/.system.journal.j9ZNZH, ACL_TYPE_ACCESS): Operation not supported (95)
rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/c5b67cb2fb4c49678a4fd62f7e4a2b20/.system.journal.9T8ypI, ACL_TYPE_ACCESS): Operation not supported (95)
rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/c5b67cb2fb4c49678a4fd62f7e4a2b20/.system@183d964d7b204812bf95ef299bd204ef-0000000000000001-0005f9239abe1277.journal.IPjN6F, ACL_TYPE_ACCESS): Operation not supported (95)
rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/c5b67cb2fb4c49678a4fd62f7e4a2b20/.system@183d964d7b204812bf95ef299bd204ef-0000000000003692-0005f9dc1d57bbfd.journal.eICVWI, ACL_TYPE_ACCESS): Operation not supported (95)

Number of files: 164,431 (reg: 128,903, dir: 31,000, link: 4,493, special: 35)
Number of created files: 164,431 (reg: 128,903, dir: 31,000, link: 4,493, special: 35)
Number of deleted files: 0
Number of regular files transferred: 128,881
Total file size: 8.86G bytes
Total transferred file size: 8.61G bytes
Literal data: 8.61G bytes
Matched data: 0 bytes
File list size: 4.98M
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 8.62G
Total bytes received: 2.63M

sent 8.62G bytes received 2.63M bytes 185.47M bytes/sec
total size is 8.86G speedup is 1.03
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3]

nun die frage ... kann man acl einfach auf dem host aktivieren?
zfs get acltype rpool/ROOT/pve-1 NAME PROPERTY VALUE SOURCE rpool/ROOT/pve-1 acltype off default

oder sollte man lieber ein eigenen Mount nehmen

zfs create -o mountpoint=/mnt/vztmp rpool/vztmp zfs set acltype=posixacl rpool/vztmp
+ anpassung des Backup Target?


oder gibt es generell eine bessere idee?

 

[fabian]

das waere eine moeglichkeit, ja. tmpdir (in /etc/vzdump.conf) muss ACLs koennen, wenn du suspend mode container backups mit ACLs machen willst.

 

[CH.illig]

ACL für den host aktivieren auch ok?

 

[fabian]

wenn /var/tmp ein normaler ordner auf / ist (mount sollte auskunft geben ), kannst du auch ACLs auf dem root dataset aktivieren, ja.

 

[CH.illig]

perfekt, dann tut es
zfs set acltype=posixacl rpool/ROOT/pve-1

vielleicht mal default bei PVE ?