@keeka @deebsr a short update: I reported this upstream as a regression in the stable kernels, and the NFS server maintainers confirmed the cause. A fix that was backported into stable Linux 7.2.4 (and the matching 6.18 kernels) leaves the ID in...
@keeka I tested both questions.
Bare metal: yes, same problem. I ran the NFS server directly on the PVE node (nfs-kernel-server on the host, exporting the same two ZFS datasets, no container). The copy between the exports hangs the same way. The...
Hi keeka,
Could you confirm with uname -r on the host that it runs 7.0.14-20-pve?
I could reproduce this in a lab with a setup like yours: a privileged Debian 12 CT exporting two ZFS datasets, and a Debian 13 client mounting with vers=4. With...
@lubosr Thanks.
I'm currently running kernel 7.0.14-20-pve. I will stick with NFS4.1 and I also disabled NFS4.2 on the lxc based server for the time being.
Re your bug report. I wondered if this issue only surfaces with that kernel and LXC or...
I have successfully been using a privileged lxc to export NFS shares for quite a while. Each share exports a separate ZFS dastaset. Mounting those shares on a Debian 13 desktop system, all file operations worked apparently flawlessly. My client...
An uneducated guess, and one that assumes the 'vma_writer_close: close failed - Host is down' is not what's implied! But, could your live guest backup be failing because you do not have qemu agent installed (VMs) or enabled (PVE guest config)...
Something I forgot: ProxmoxVE9 introduced a new, still in tech-preview-feature which allows converting oci ( aka docker ) container images to lxcs. To be honest I'm not a big fan since this procedure destroys the immutability which is the biggest...
Here's my current thoughts/opinions about running docker/podman in CTs
- It currently works fine (at least in a debian CT)
- It might break on docker (related) or kernel updates
- Breakage is likely to be fixed soon but you'll have to be patient...