Search results

So.. I have found a solution :-) I wiped the machine - installed proxmox 1.9 & kernel 2.6.18-6-pve Not a single io lockout since doing this!

so... I have gone through every tunable setting possible.. comparing to the previous 1.X series kernels. Nothing works. Without fail.. high io.. and the system stalls. What is strange... you would think the disks would be thrashing - but the dont! They are realatively idle, yet the OS is...

Sadly.. yes :-) I have managed to 'stabilize' the system through various tweaks... But nothing sorts it once and for all. To give an idea... just an rsync to migrate a machine will bring the server to it's knees! It is really quite a major problem! Consider... pretty much most...

If I am correct you are based on the redhat/centos tree? See... https://bugzilla.redhat.com/show_bug.cgi?id=790638 I have been fighting this issue for days now. No amount of tuning eliminates the issue. In short.. High io results in the raid driver going into a hung state. rob

Hello, Is it possible to use an earlier firmware version on proxomox 2.0? There is a serious compatability issue with the lsi raid controller's on the current version. Rob

So.. After yet another crash... I started again and this time - 1 hour on things are looking ok! To load test I have multiple dd commands running, and rsync & a vsdump! So.. settings as follows: echo cfq > /sys/block/sda/queue/scheduler echo 0 > /sys/block/sda/queue/iosched/slice_idle...

Hello, I have recently installed 6 new super micro servers. Each of these has been experiencing various issues related to disk io under proxmox 2. I have been working through a variety of fixes for these issues - and have now got the following 'working' platform in place. Still early...

So... Changed the controller to the 9660 with 512MB and the lvm creates and removes work! Sweet!

At least not only me :) Seems it is an issue in the redhat tree. Rob Sent from my iPhone using Tapatalk

Here you go.. root@cloud0:~# pveversion -v pve-manager: 2.0-38 (pve-manager/2.0/af81df02) running kernel: 2.6.32-7-pve proxmox-ve-2.6.32: 2.0-60 pve-kernel-2.6.32-7-pve: 2.6.32-60 lvm2: 2.02.88-2pve1 clvm: 2.02.88-2pve1 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-2 libqb: 0.10.1-2...

Oh... I see what you mean now! It would be good if these could 'match up'. Unfortuantly the interface actually seems to not like it if the interfaces do not follow a naming convention of VMBRXXX This means you end up with a weird mapping. I keep a spreadsheet with all of this in it! Rob

See this extract auto vmbr0 iface vmbr0 inet static address 192.168.21.100 netmask 255.255.255.0 gateway 192.168.21.1 bridge_ports eth0 bridge_stp off bridge_fd 0 auto vmbr1 iface vmbr1 inet manual bridge_ports eth0.10...

Hello, I run a bacula backup system and have some scripts that automatically create an lvm snapshot of /var/lib/vz prior to backup. Since the update to version two.... I get this error when I unmount the snapshot: -- Attempt 1 Unable to deactivate open pve-data-real (253:4) Failed to...

Hello, Yes. This is possible. I do it on my setup. Take a look at /etc/interfaces and modify it to suit! Rob

This thread... http://forum.proxmox.com/threads/8661-Proxmox-soft-lockups-on-megaraid-controller?p=49095#post49095 Seems to have an answer! At least in my initial tests! In summary.... # this option stops the disk soft lockups! echo 0 > /sys/block/sda/queue/iosched/slice_idle

Intesting post... your solution seems to work better than mine! Nice :-)

I have had very similar issues on my boxes - and have not found a conclusive fix. In my case I have assumed the issue seems to be the lsi megaraid controllers. The io timout issues seem to have many bug reports on redhat relating to the 120 second timeout. Changing the disk scheduler to...

Hi All, I have a proxmox sytem that has been installed onto a raid 10 system running on a LSI megaraid controller. Now.. it seems that their are some issues in that the system will hang up when the drives are being driven hard. Not a crash as such - but the system seems to get into a state...

I have had a range of proxmox 1 series. 1.7 - 1.9. All you do is install the SSH keys on the node so you can logon with no password. Then... 1 by 1. vzmigrate --keep-dst --remove-area no -v <proxmox2 ip> <ct id> Do not try do an online migration. This will not work. Rob

I have just finished a migration. 30 or do boxes using vz migrate. Worked perfectly! Sent from my iPhone using Tapatalk