<div dir="ltr"><div>Hello list,</div><div><br></div><div>I have a single node running a single vm (win2k3).</div><div>It was working fine on Proxmox 2.3.I upgraded this box to 3.1 last week by following:</div><div><a href="http://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0">http://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0</a>.<br>
</div><div>All went smooth, except that backup is not completed for some reason.</div><div>I have a local nfs mount on a NAS device which I use as a backup target:</div><div><br></div><div><div>root@proxmox1:~# df -h</div>
<div>Filesystem Size Used Avail Use% Mounted on</div><div>udev 10M 0 10M 0% /dev</div><div>tmpfs 194M 1.5M 192M 1% /run</div><div>/dev/mapper/pve-root 28G 16G 11G 60% /</div>
<div>tmpfs 5.0M 0 5.0M 0% /run/lock</div><div>tmpfs 387M 22M 366M 6% /run/shm</div><div>/dev/mapper/pve-data 65G 9.8G 55G 16% /var/lib/vz</div><div>
/dev/sda1 495M 123M 348M 27% /boot</div><div>/dev/fuse 30M 16K 30M 1% /etc/pve</div><div><b>192.168.0.203:/VOLUME1/PUBLIC 442G 198G 244G 45% /mnt/pve/nfs1</b></div></div>
<div><b><br></b></div><div>The error I am receiving is:</div><div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px"><b>VM 101 qmp command 'query-backup' failed - client closed connection</b></span><br>
</div><div><span style="font-family:arial,sans-serif;font-size:13px"><b><br></b></span></div><div><font face="arial, sans-serif">What I've noticed is that if even if I invoke a manual backup job, the process starts but it takes forever and then stops with the above message.</font></div>
<div>During this time, if I ping the node I get very high response time and some times it is near inaccessible.</div><div>I did a test to write a 100mb file at nfs mount:</div><div><br></div><div><div><b>root@proxmox1:~# dd if=/dev/zero of=/mnt/pve/nfs1/test.raw bs=1M count=100</b></div>
<div><b>100+0 records in</b></div><div><b>100+0 records out</b></div><div><b>104857600 bytes (105 MB) copied, 340.931 s, 308 kB/s</b></div></div><div><b><br></b></div><div>Seems that for some reason the machine has a hard time communicating with NAS device.The strange thing is that before upgrade there was no problem.</div>
<div>Could it be a nic driver issue? I'm providing some more info if could anyone help:</div><div><br></div><div><br></div><div><div><b>root@proxmox1:~# pveversion -v</b></div><div><b>proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)</b></div>
<div><b>pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)</b></div><div><b>pve-kernel-2.6.32-20-pve: 2.6.32-100</b></div><div><b>pve-kernel-2.6.32-16-pve: 2.6.32-82</b></div><div><b>pve-kernel-2.6.32-17-pve: 2.6.32-83</b></div>
<div><b>pve-kernel-2.6.32-18-pve: 2.6.32-88</b></div><div><b>pve-kernel-2.6.32-23-pve: 2.6.32-109</b></div><div><b>lvm2: 2.02.98-pve4</b></div><div><b>clvm: 2.02.98-pve4</b></div><div><b>corosync-pve: 1.4.5-1</b></div><div>
<b>openais-pve: 1.1.4-3</b></div><div><b>libqb0: 0.11.1-2</b></div><div><b>redhat-cluster-pve: 3.2.0-2</b></div><div><b>resource-agents-pve: 3.9.2-4</b></div><div><b>fence-agents-pve: 4.0.0-1</b></div><div><b>pve-cluster: 3.0-7</b></div>
<div><b>qemu-server: 3.1-1</b></div><div><b>pve-firmware: 1.0-23</b></div><div><b>libpve-common-perl: 3.0-6</b></div><div><b>libpve-access-control: 3.0-6</b></div><div><b>libpve-storage-perl: 3.0-10</b></div><div><b>pve-libspice-server1: 0.12.4-1</b></div>
<div><b>vncterm: 1.1-4</b></div><div><b>vzctl: 4.0-1pve3</b></div><div><b>vzprocps: 2.0.11-2</b></div><div><b>vzquota: 3.1-2</b></div><div><b>pve-qemu-kvm: 1.4-17</b></div><div><b>ksm-control-daemon: 1.1-1</b></div><div><b>glusterfs-client: 3.4.0-2</b></div>
</div><div><br></div><div><br></div><div><div><b>root@proxmox1:~# tail /var/log/kern.log</b></div><div><b>Sep 16 02:35:11 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div><div><b>Sep 16 10:18:47 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div>
<div><b>Sep 16 10:19:35 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div><div><b>Sep 16 10:20:05 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div><div><b>Sep 16 10:20:35 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div>
<div><b>Sep 16 10:20:59 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div><div><b>Sep 16 10:21:41 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div><div><b>Sep 16 10:22:05 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div>
<div><b>Sep 16 10:22:41 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div><div><b>Sep 16 10:23:11 proxmox1 kernel: r8169 0000:02:00.0: eth0: link up</b></div></div><div><br></div><div><br></div><div><br></div><div>
<br></div><div><br></div><div><br></div><div><br></div><div><br><br><div> <br><div><br></div></div></div>
</div>