Funnily, I found a relevant Reddit thread a few minutes after this one:
I can confirm the recursive mount works! However, I don't like the fact that Proxmox doesn't show these entries in the Resources tab like 'native' mounts.
Ok, this was a zfs dataset issue on the nfs server. The data is actually there on the nfs server. mounting the zfs dataset was what I had to do to see the actual data.
Thanks Fiona for correctly pointing out I'm not following the instructions https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline
Running the following resolves the errors:
sed -i s/"quiet"/"quiet intel_iommu=off"/g...
Update: in the mean time, it has finished the second round:
INFO: starting first sync /proc/71143/root/ to /var/tmp/vzdumptmp777200_104
INFO: first sync finished - transferred 391.30G bytes in 27610s
INFO: suspending guest
INFO: starting final...
In the "options" (fourth) field (see the description in the first line of your file), i.e.:
nas.localdomain:/volumes/raid2/pve_pbs /network/pve_pbs nfs,vers=3 async,_netdev 0 0
(fields are separated by tabs or spaces).
BTW: probably not...
Thanks that seems to have worked! Boots up immediately now with no error. So this is what the fstab line looks like now:
nas.localdomain:/volumes/raid2/pve_pbs /network/pve_pbs nfs,vers=3 async,_netdev 2 0
Hi all,
I recently (and temporarily) switched storage backend for a container from snapshot capable to not snapshot capable.
Now the backup makes two rounds:
rsync while live to temp storage
suspend container and rsync again for verification...