Recent content by HostVPS

As I mentioned above, fast fsck times on large RAID arrays when using ext4 was the biggest factor for me. Have you seen https://bugzilla.openvz.org/show_bug.cgi?id=2085 ? Looks like your bug... no?

Sorry, wish I could help, but we're not running quota on these nodes. Just looking at your thread and I agree with your comments regarding ext4 vs ext3 - ext3 is just too slow for fscks on the large arrays we have these days, hope you get this sorted.

I updated one of our prevously affected nodes to the new kernel pve-kernel-2.6.32-19 (2.6.32-95) from the pvetest repository today, which is based on the latest OpenVZ Kernel vzkernel-2.6.32-042stab076.5.src.rpm and we can now run OpenVZ LVM Snapshot backups again using ext4 without the LVM...

Thanks for the good advice, I'll look into doing that. Regards, Bob

Many thanks for the info Tom, it's back to the drawing board for me then! We were fine with ext4 until PVE-2.3 with the 2.6.32-18-pve kernel, even running PVE-2.3 works with 2.6.32-17-pve, but 2.6.32-18-pve and the testing 2.6.32-19-pve kernels are not stable over three different hardware...

Hi Tom, I've done over a dozen LVM snapshot backup tests on both nodes now and I have not seen a single crash or problem with PVE-2.3 with the current 2.6.32-18-pve kernel as long as you run ext3 NOT ext4. Regarding configs: I reinstalled two of the affected nodes, one box running a 3WARE...

Thanks Tom, I came to the same conclusion and rebuilt one of the affected nodes using ext3, I'm testing now on a fresh PVE-2.3 install with the current default kernel and have not seen any LVM snapshot problems so far, weird that LVM snapshots with ext4 had run without issue until this latest...

Do you guys use and test against both ext3 and ext4 on your test lab servers? As we are running on ext4 and this is a non-default install option that we told the Proxmox installer to use when setting all these nodes up.

Hi Tom, I completely follow what your saying. Just to confirm the details, these nodes were simply installed using the latest version of Proxmox 2.* with no changes to any of the standard Proxmox configuration. Our servers are all running on the last three generations of Intel main boards and...

Update: The LVM snapshot problem still exists when using the latest testing PVE kernel 2.6.32-19-pve ( I have tried both 2.6.32-19-pve_2.6.32-92 and 2.6.32-19-pve_2.6.32-93 ). The PVE volume group locks as soon as you start the snapshot backup and occurs most of the time apart from the odd...

Done! :) We could really do with this in WHMCS.

Hi Dietmar, I installed the latest 2.6.32-19-pve kernel from pvetest last night and left two previously affected nodes with different hardware configurations ( one box running a 3WARE 9690SA RAID card the other LSI MR9260 with different CPUs and main boards ) running overnight doing large LVM...

Hi Tom, Thanks for your reply, but I don't think a remote support login to just one of our servers with the LVM problem is going to help as it's affecting several servers with completely different hardware configurations, the only common thing is the new PVE version. I've just found that if I...

Sorry, I thought the details had changed enough to warrant a new thread as this fault is now affecting several different server configurations and not just an issue with LSI RAID cards drivers as I first thought. I have spent a lot of time over the last week trying to find more facts. The only...

Hi, Since we upgraded our nodes to PVE-2.3 we cannot use LVM snapshot backups anymore on OpenVZ CT's, if we do the LVM sub-system just locks up, we lose all drive IO and are forced to reboot the node. At first I thought this was an issue with the LSI RAID card drivers on two of our newer...