Warning: Cannot acl_from_text

[Chentoa]

Hi,
I just got this TAR warning when I restored an LXC backup to a new Proxmox server (5.3) :

$ sudo pct restore 1011 /home/.DATA1/BACKUPS/dump/vzdump-lxc-1011-2019_03_22-23_24_38.tar.lzo --storage disks --force true
(...)
extracting archive '/home/.DATA1/BACKUPS/dump/vzdump-lxc-1011-2019_03_22-23_16_05.tar.lzo'
tar: ./var/log/journal/aa3150f25d464ea3b87db8cfe20764af/user-1000@766432c4934648909cdfc73b30085070-00000000008bc677-000581effacd9436.journal: Warning: Cannot acl_from_text
tar: ./var/log/journal/aa3150f25d464ea3b87db8cfe20764af/user-1000@766432c4934648909cdfc73b30085070-00000000009a3912-00058388ee39fe89.journal: Warning: Cannot acl_from_text
(...)

Is it something I should worry about ? The restored container seems to work fine

 

[valbuz]

Hi,
I just got this TAR warning when I restored an LXC backup to a new Proxmox server (5.3) :

$ sudo pct restore 1011 /home/.DATA1/BACKUPS/dump/vzdump-lxc-1011-2019_03_22-23_24_38.tar.lzo --storage disks --force true
(...)
extracting archive '/home/.DATA1/BACKUPS/dump/vzdump-lxc-1011-2019_03_22-23_16_05.tar.lzo'
tar: ./var/log/journal/aa3150f25d464ea3b87db8cfe20764af/user-1000@766432c4934648909cdfc73b30085070-00000000008bc677-000581effacd9436.journal: Warning: Cannot acl_from_text
tar: ./var/log/journal/aa3150f25d464ea3b87db8cfe20764af/user-1000@766432c4934648909cdfc73b30085070-00000000009a3912-00058388ee39fe89.journal: Warning: Cannot acl_from_text
(...)

Is it something I should worry about ? The restored container seems to work fine

Do you find a solution?

 

[jAston]

reproducible with
proxmox-ve: 8.2.0 (running kernel: 6.8.12-3-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)

 

[fiona]

Hi,
what does stat /path/to/problematic/file in the container tell you? On the host, does running pct fsck <ID> (optionally adding --device mp<N> if the file is on a mount point) help?

 

[jAston]

Hi,
what does stat /path/to/problematic/file in the container tell you? On the host, does running pct fsck <ID> (optionally adding --device mp<N> if the file is on a mount point) help?

stat: cannot statx '/var/log/journal/xyz.journal': No such file or directory

pct fsck 101:
unable to run fsck for 'XYZ:subvol-101-disk-0' (format == subvol)

 

[fiona]

pct fsck 101:
unable to run fsck for 'XYZ:subvol-101-disk-0' (format == subvol)

Is this ZFS? Please check zpool status and whether you can see (and stat) the problematic files in the associated directory on the host then (pvesm path XYZ:subvol-101-disk-0).

 

[jAston]

Hi,
what does stat /path/to/problematic/file in the container tell you? On the host, does running pct fsck <ID> (optionally adding --device mp<N> if the file is on a mount point) help?

Oh, I've done it wrong the first time I guess.

'stat' On the LXC:
Access: (0640/-rw-r-----) Uid: ( 0/ root) Gid: ( 999/systemd-journal)

And yes, ZFS.