write: File too large

stef1777

Active Member
Jan 31, 2010
178
8
38
Hello!

I need to some help. A vzdump backup of one the VM stop on error.

write: File too large

I'm trying to backup a 32Go (real used space) VM on a NFS vzdump volume. The node have 31Go free on pve-root and 60G free on pve-data. The nfs volume have 800Go free.

Each time the backup start, it finish with the following error:

Feb 06 09:37:09 INFO: Starting Backup of VM 101 (openvz)
Feb 06 09:37:09 INFO: CTID 101 exist mounted running
Feb 06 09:37:09 INFO: status = CTID 101 exist mounted running
Feb 06 09:37:09 INFO: backup mode: snapshot
Feb 06 09:37:09 INFO: bandwidth limit: 10240 KB/s
Feb 06 09:37:09 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-aweb-vs001-0')
Feb 06 09:37:10 INFO: Logical volume "vzsnap-aweb-vs001-0" created
Feb 06 09:37:10 INFO: creating archive '/mnt/pve/Backup-VZDump/vzdump-openvz-101-2010_02_06-09_37_01.tgz'
Feb 06 09:40:35 INFO: 2147483647 B 2.0 GB 204.8 s (3:24 min) 10485799 B/s 10.00 MB/s
Feb 06 09:40:35 INFO: write: File too large
Feb 06 09:40:36 INFO: Logical volume "vzsnap-aweb-vs001-0" successfully removed
Feb 06 09:40:37 ERROR: Backup of VM 101 failed - command '(cd /mnt/vzsnap0/private/101;find . '(' -regex '^\.$' ')' -o '(' -type 's' -prune ')' -o -print0|tar czpf - --totals --sparse --numeric-owner --no-recursion --ignore-failed-read --one-file-system --null -T - |cstream -t 10485760 >/mnt/pve/Backup-VZDump/vzdump-openvz-101-2010_02_06-09_37_01.dat )' failed with exit code 2

I tried with and without compression with the same result.

I tried to figure where come from the problem but I was unsuccessful.
 
Hi,
Feb 06 09:40:35 INFO: 2147483647 B 2.0 GB 204.8 s (3:24 min) 10485799 B/s 10.00 MB/s
Feb 06 09:40:35 INFO: write: File too large
the backup can only write 2GB (some old filesystems and nfs-v2 has this limit).
What kind of filesystem is the nfs-share and which nfs-version do you use?

Can you produce on the nfs-server a 32GB-file on the share?

Udo
 
Oh, great. Thanks. I solved it. It was a problem with the version of the NFS server. I'm running NFS v4 now. All is fine.