[SOLVED] vzdump failure with stopped LXC: .zfs/shares EOPNOTSUPP: Operation not supported on transport endpoint

[hvisage]

Good day,

Busy cleaning up LXCs that I had shutdown, but seems to keep getting this error with the methods SNAPSHOT & STOPPED
Backup works fine after starting the LXC, but want to backup the "downed" LXCs with the troubles/issues that could happen with starting these (if any)

Spoiler: vzdump output

INFO: starting new backup job: vzdump 801099 --storage T4A-backups --remove 0 --notes-template 'archival backup - {{cluster}}, {{guestname}}, {{node}}, {{vmid}}' --mode stop --node trosdata01-lim03
INFO: Starting Backup of VM 801099 (lxc)
INFO: Backup started at 2022-11-30 12:05:06
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 8
INFO: CT Name: sbg-objectstore-recovery
INFO: including mount point rootfs ('/') in backup
INFO: including mount point mp0 ('/data') in backup
INFO: creating Proxmox Backup Server archive 'ct/801099/2022-11-30T12:05:06Z'
INFO: run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=encrypt --keyfd=16 pct.conf:/var/tmp/vzdumptmp4092833_801099/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --include-dev /mnt/vzsnap0/./data --skip-lost-and-found --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 801099 --backup-time 1669809906 --repository tros@pbs!backups@pbs-01.fqdn.fqdn:DataStoreName
INFO: Starting backup: ct/801099/2022-11-30T12:05:06Z
INFO: Client name: trosdata01-lim03
INFO: Starting backup protocol: Wed Nov 30 12:05:06 2022
INFO: Using encryption key from file descriptor..
INFO: Encryption key fingerprint: f7:ce:55:77:29:05:55:33
INFO: Downloading previous manifest (Sat Jul  9 04:08:45 2022)
INFO: Upload config file '/var/tmp/vzdumptmp4092833_801099/etc/vzdump/pct.conf' to 'tros@pbs!backups@pbs-01.fqdn.fqdn:8007:DataStoreName' as pct.conf.blob
INFO: Upload directory '/mnt/vzsnap0' to 'tros@pbs!backups@pbs-01.fqdn.fqdn:8007:DataStoreName' as root.pxar.didx
INFO: catalog upload error - channel closed
INFO: Error: error at ".zfs/shares": EOPNOTSUPP: Operation not supported on transport endpoint
ERROR: Backup of VM 801099 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=encrypt' '--keyfd=16' pct.conf:/var/tmp/vzdumptmp4092833_801099/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --include-dev /mnt/vzsnap0/./data --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 801099 --backup-time 1669809906 --repository tros@pbs!backups@pbs-01.fqdn.fqdn:DataStoreName' failed: exit code 255
INFO: Failed at 2022-11-30 12:05:06
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[fabian]

either set the snapdir property of the dataset to hidden, or exclude the .zfs dir from backups.

 

[timdonovan]

either set the snapdir property of the dataset to hidden, or exclude the .zfs dir from backups.

What does this even mean? How is it related to an LXC backup? What dataset? What zfs dir? I'm not sure what this advice means in the context of "my LXC failed to backup with the following error"

 

[fabian]

I am not sure what those questions are supposed to mean? OP had an issue that was caused by them using ZFS storage in way that is not compatible with vzdump (it's clear from the error message they posted), I told them how to fix it on either the ZFS or the vzdump end..

 

[timdonovan]

@fabian fair enough,I apologise. But when the Proxmox UI throws this error, and literally the ONLY thread on Google is this thread, your post doesn't give any clarity as to how to diagnose or solve the issue, or even the root cause. I have a standard OOTB LXC and it's throwing this error.

"set the snapdir property of the dataset"

set - how to set it?
snapdir property - whats that? Why? Don't see it in the PVE manual
dataset? Ok, a bit of a clue here, you want us to modify our zpool because..?

"exclude the .zfs dir from backups"

exclude - how?
the .zfs dir - what .zfs dir?

 

[timdonovan]

I fixed this anyway by starting my LXC. That seem to allow PVE to back it up without this error. I don't know why. Another day, another generic "255" error code...

 

[fabian]

I never said those steps would fix every occurrence of that exit code the exit code in this case is only the "symptom", the cause is a few lines above and very specific to this particular user's setup.

if you encounter an issue where the errors are not understandable to you (or the cause is not obvious), feel free to post here (in a new thread ) - but please provide the task log and any relevant details about your setup (such as guest and storage config, installed package versions, ..).