Backup of some machines failes

L

lemonbiter

New Member
Sep 3, 2023
21
0
1
Germany
Hi there
I have connected a USB HDD directly to a VM that runs Openmediavault. I have added a folder to that HDD as CFIS/SMB device for backups.
I am able to make backups of some LXS with success to this folder, but one LXC is larger than 3 GB and it failes permanently - i tried both, suspend and stopped mode.
The backup begins and after approx. 2.4 GB it "hangs", and the SMB share is ... gone? I need to stop the backup manually as it never ends and restart the VM with openmediavault to get the SMB share back. When I send larger files like 10GB via SMB with no issue from windows, the size of the backup dows not seem to be the isseu I guess

Any suggestions - if so... please use simple words... I am a total newby to PM and linus in general... I need low low low level support... yes, the poswer cable is connected :)
Thanks

LEM
 
Hello

I would recommend you
  • Listen to the journal with journalctl -f
  • Attempt an backup
  • Post the output of the journalctl here
 
Philipp Hufnagl said:
Hello

I would recommend you
  • Listen to the journal with journalctl -f
  • Attempt an backup
  • Post the output of the journalctl here
Click to expand...
Hi Philip
The drive was online and available before I started the job. Its name is: WD5TBBackup2. I started the job and here is the result (please ignore the "Proxmox-Backups-QNAP" as that device is offline)

The moment I started the job the device became unavailable and I had to restart the VM with OVM to get access back...

Code: 
Oct 02 13:39:58 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:40:01 pve kernel: CIFS: VFS: \\192.168.2.102 Error -32 sending data on socket to server
Oct 02 13:40:01 pve kernel: CIFS: VFS: \\192.168.2.102 Error -32 sending data on socket to server
Oct 02 13:40:06 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:40:06 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:40:06 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:40:08 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:40:15 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:40:15 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:40:15 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:40:21 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:40:21 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:40:24 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:40:27 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:40:27 pve pvestatd[998]: status update time (6.195 seconds)
Oct 02 13:40:31 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:40:31 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:40:36 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:40:36 pve pvestatd[998]: status update time (5.213 seconds)
Oct 02 13:40:42 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:40:42 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:40:46 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:40:51 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:40:51 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:40:52 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:40:55 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:41:02 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:41:07 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:41:07 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:41:07 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:41:07 pve pvestatd[998]: status update time (6.378 seconds)
Oct 02 13:41:09 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:41:11 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:41:11 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:41:16 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:41:16 pve pvestatd[998]: status update time (5.189 seconds)
Oct 02 13:41:21 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:41:22 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:41:25 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:41:28 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:41:33 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:41:38 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:41:38 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:41:38 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:41:38 pve pvestatd[998]: status update time (6.377 seconds)
Oct 02 13:41:38 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:41:41 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:41:41 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:41:43 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:41:47 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:41:47 pve pvestatd[998]: status update time (6.117 seconds)
Oct 02 13:41:51 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:41:51 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:41:53 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:41:56 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:41:56 pve pvestatd[998]: status update time (5.294 seconds)
Oct 02 13:41:57 pve pveproxy[249694]: worker exit
Oct 02 13:41:57 pve pveproxy[1036]: worker 249694 finished
Oct 02 13:41:57 pve pveproxy[1036]: starting 1 worker(s)
Oct 02 13:41:57 pve pveproxy[1036]: worker 556268 started
Oct 02 13:42:04 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:42:05 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:42:05 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:42:05 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:42:09 pve kernel: nfs: server 192.168.2.100 not responding, timed out
Oct 02 13:42:15 pve pvestatd[998]: storage 'Proxmox-Backups-QNAP' is not online
Oct 02 13:42:15 pve pvestatd[998]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5
Oct 02 13:42:15 pve pvestatd[998]: storage 'WD5TBBackup2' is not online
Oct 02 13:42:19 pve kernel: nfs: server 192.168.2.100 not responding, timed out

after restarting the VM with OVM and starting the other job which contains several other LXC's it works... It is just the one LXC that has the issue... I guess file size might be the problem? ... This LXC uses 11.11 GiB) ... When I run the same job to an NFS share on my QNAP it all works... But I wonder why this is the case and how I could fix it


Code: 
 Status running
 HA-Status keine
 Knoten pve
 CPU-Auslastung 0.75% von 8 CPU(s)
 Speicherverbrauch 31.05% (2.48 GiB von 8.00 GiB)
 SWAP-Auslastung 0.00% (0 B von 512.00 MiB)
 Bootdisk-Größe 14.21% (11.11 GiB von 78.19 GiB)

Code: 
Header
Proxmox
Virtual Environment 8.0.4
Suche
Rechenzentrum
Server-Ansicht
Logs
()
INFO: starting new backup job: vzdump 201 202 300 400 --node pve --mailto peter@hytrek.de --all 0 --mailnotification always --mode snapshot --storage WD5TBBackup2 --notes-template '{{guestname}}' --compress zstd
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp7010_201 for temporary files
INFO: Starting Backup of VM 201 (lxc)
INFO: Backup started at 2023-10-02 14:16:46
INFO: status = running
INFO: CT Name: Influx
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
  Logical volume "snap_vm-201-disk-0_vzdump" created.
INFO: creating vzdump archive '/mnt/pve/WD5TBBackup2/dump/vzdump-lxc-201-2023_10_02-14_16_46.tar.zst'
INFO: Total bytes written: 4573542400 (4.3GiB, 485MiB/s)
INFO: archive file size: 1.91GB
INFO: adding notes to backup
INFO: cleanup temporary 'vzdump' snapshot
  Logical volume "snap_vm-201-disk-0_vzdump" successfully removed.
INFO: Finished Backup of VM 201 (00:00:24)
INFO: Backup finished at 2023-10-02 14:17:10
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp7010_202 for temporary files
INFO: Starting Backup of VM 202 (lxc)
INFO: Backup started at 2023-10-02 14:17:10
INFO: status = running
INFO: CT Name: Grafana
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
  Logical volume "snap_vm-202-disk-0_vzdump" created.
INFO: creating vzdump archive '/mnt/pve/WD5TBBackup2/dump/vzdump-lxc-202-2023_10_02-14_17_10.tar.zst'
INFO: Total bytes written: 1344983040 (1.3GiB, 221MiB/s)
INFO: archive file size: 507MB
INFO: adding notes to backup
INFO: cleanup temporary 'vzdump' snapshot
  Logical volume "snap_vm-202-disk-0_vzdump" successfully removed.
INFO: Finished Backup of VM 202 (00:00:08)
INFO: Backup finished at 2023-10-02 14:17:18
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp7010_300 for temporary files
INFO: Starting Backup of VM 300 (lxc)
INFO: Backup started at 2023-10-02 14:17:18
INFO: status = running
INFO: CT Name: piHole
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
  Logical volume "snap_vm-300-disk-0_vzdump" created.
INFO: creating vzdump archive '/mnt/pve/WD5TBBackup2/dump/vzdump-lxc-300-2023_10_02-14_17_18.tar.zst'
INFO: Total bytes written: 827607040 (790MiB, 200MiB/s)
INFO: archive file size: 271MB
INFO: adding notes to backup
INFO: cleanup temporary 'vzdump' snapshot
  Logical volume "snap_vm-300-disk-0_vzdump" successfully removed.
INFO: Finished Backup of VM 300 (00:00:06)
INFO: Backup finished at 2023-10-02 14:17:24
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp7010_400 for temporary files
INFO: Starting Backup of VM 400 (lxc)
INFO: Backup started at 2023-10-02 14:17:24
INFO: status = running
INFO: CT Name: docker
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
  Logical volume "snap_vm-400-disk-0_vzdump" created.
INFO: creating vzdump archive '/mnt/pve/WD5TBBackup2/dump/vzdump-lxc-400-2023_10_02-14_17_24.tar.zst'
INFO: Total bytes written: 2319175680 (2.2GiB, 196MiB/s)
INFO: archive file size: 756MB
INFO: adding notes to backup
INFO: cleanup temporary 'vzdump' snapshot
  Logical volume "snap_vm-400-disk-0_vzdump" successfully removed.
INFO: Finished Backup of VM 400 (00:00:16)
INFO: Backup finished at 2023-10-02 14:17:40
INFO: Backup job finished successfully
TASK OK
 
Last edited:
For now I am leaning more towards network issue. Do you just "see" the drive online or did you actually manage to use it?

Also lets digg deeper with sudo cat /etc/pve/storage.cfg lsblk and cat /etc/pve/qemu-server/<vmid>.conf
 
You must log in or register to reply here.
Top Bottom