So I tried to find an open process that was associated with /dev/pve/vzsnap-cassiusclay-0 but neither fuser or lsof lists anything. So I stopped both VMs, then I was able to remove /dev/pve/vzsnap-cassiusclay-0. I then did a snapshot and both VMs backed up fine. We'll just have to wait and see...
My scheduled backups have failed on me the last couple of nights. I don't really don't know where to start on troubleshooting this one. Any help would be appreciated. The only thing unique about these guests is they are the only Windows guests in my cluster.
vzdump 100 101 102 103 104 105...
I didn't have an extra slot, so I just switched out the slots that cards were in. Lo and behold everything works fine now. I wish I could I could say I understand why but I don't. Regardless, thanks for ideas Tom.
-Dave
Thanks for the reply Tom. Here is the output from pveversion -v:
root@cassiusclay:~# pveversion -v
pve-manager: 2.0-18 (pve-manager/2.0/16283a5a)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-55
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve...
I have a test server I am setting up the has 4 nics installed. 2 are onboard Intel using the e1000 driver. 2 are addons and are using the r8169 driver. The problem is that only 1 of the 2 r8169's succesfully loads on boot. See the following truncated dmesg output:
r8169 Gigabit Ethernet driver...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.