Hello everyone,
We have a Dell Unity storage system that exports an NFS 4.2 volume to our Proxmox 8.4.1 cluster.
The VMs with their disk images on it run normally without any issues.
The problems are :
- When the Proxmox backup job is triggered, the disk images read by the hypervisors only contain zeros.
- When the disk image is moved out of the Dell Unity storage, the destination disk is also full of zeros and the VM ceases to function.
On the joined picture, you can see the backup size before we moved to the unity storage and after.
The strange thing is that accessing the disk image from any Hypervisor Shell works correctly.
- "du -h" shows the correct size
- "hexdump" at a random place shows the data
- "cp" of the disk image to another location (out of the Dell Unity storage) copies the expected data
Also, it seems that some VMs are not affected.
What could cause 'vzdump' and the disk move to fail like that?
Do these commands or features access the storage differently?
Thank you in advance for your help.
We have a Dell Unity storage system that exports an NFS 4.2 volume to our Proxmox 8.4.1 cluster.
The VMs with their disk images on it run normally without any issues.
The problems are :
- When the Proxmox backup job is triggered, the disk images read by the hypervisors only contain zeros.
- When the disk image is moved out of the Dell Unity storage, the destination disk is also full of zeros and the VM ceases to function.
On the joined picture, you can see the backup size before we moved to the unity storage and after.
The strange thing is that accessing the disk image from any Hypervisor Shell works correctly.
- "du -h" shows the correct size
- "hexdump" at a random place shows the data
- "cp" of the disk image to another location (out of the Dell Unity storage) copies the expected data
Also, it seems that some VMs are not affected.
What could cause 'vzdump' and the disk move to fail like that?
Do these commands or features access the storage differently?
Thank you in advance for your help.