Search results

But no ideas ?

Hi, ok, sorry, I edited my post.

Hello ! After a SSH connexion, I got theses message on login : -bash: [: too many arguments -bash: [: =: unary operator expected -bash: [: =: unary operator expected -bash: [: too many arguments -bash: [: too many arguments So, I made an apt-get update & apt-get upgrade I saw these message...

Hi, I switched to CFQ, retry the backup and it's still the same. When doing a backup in STOP mode, everything is working fine, but in SNAPSHOT MODE, the vzdump process works and hang just before releasing the LVM snapshot. The is a .tar.lzo file so the backup seems to be ok, but the server go in...

I'll try this, but I think it comes from another thing as the other server works fine on the same network, on the same Nas for backup and with the latest proxmox version. The difference is the other server use SOFT raid.

It should not be slow, but I can make tests. For information, I have another proxmox 3 that backup on this NFS server and everything works great ... What would you recommand as a limitation or test ?

Here is the vzdump command I used : vzdump 207 --mode snapshot --compress lzo --storage nas So, I think I used LZO ... cat /etc/pve/storage.cfg nfs: nas path /mnt/pve/nas server 10.16.101.124 export /nas-002704/backup/ options vers=3 content images,rootdir,backup maxfiles 3 dir: local...

Hi ! I upgraded to the last kernel this night, and the problem still exist ... The backup worked good for 2 VM, and then, same problem on the lvremove and load growing high ... And nothing could be done, unless HARD REBOOT ... He are are the spec of my server ...

OK, I will try this and keep you updated.

pveversion -v pve-manager: 3.0-23 (pve-manager/3.0/957f0862) running kernel: 2.6.32-20-pve proxmox-ve-2.6.32: 3.0-100 pve-kernel-2.6.32-20-pve: 2.6.32-100 lvm2: 2.02.95-pve3 clvm: 2.02.95-pve3 corosync-pve: 1.4.5-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2...

Hi, +1 for this problem ! I have just "size: 4000" in /etc/vzdump.conf VG #PV #LV #SN Attr VSize VFree pve 1 2 0 wz--n- 1.80t 100.00g pve-manager: 3.0-23 (pve-manager/3.0/957f0862) running kernel: 2.6.32-20-pve proxmox-ve-2.6.32: 3.0-100 pve-kernel-2.6.32-20-pve: 2.6.32-100...

+1 We have the same issue on one of our server since upgrade from 2.3 to 3.0. The other fresh 3.0 server works fine with the same parameters. We backup on NFS.

Thanks !!! Why is pve-qemu-kvm important ? Is there a link with my problem ? <code> pveversion -v pve-manager: 1.8-18 (pve-manager/1.8/6070) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-33 pve-kernel-2.6.32-4-pve: 2.6.32-33 qemu-server: 1.1-30 pve-firmware: 1.0-11 libpve-storage-perl...

Ah ! How do I add this ? I am only using openvz VM, is it needed ? Thanks for your reply, Aurélien.

Hi, Thanks for the answer, I already saw your thread, but It's strange for the kernel 2.6.32, it seems to be the default one, I didn't choose to install this one. I can't test neither to downgrade in 2.6.18, but maybe will try with a new server soon. Perhaps they'll find a solution soon...

Hi Everybody, Just another post to signal the problem of VM that could not been restarted... When this happens, I can't do nothing, enter in vm, ping, ssh, stop, retard, kill -9 ... Nothing is working... I found no solution except from rebooting the proxmox machine... That's not a good...