Search results

Maybe i could immagine what you want to do but seems too risky and complicated to use it in a production environment. By the kernel plz read the other posts. Ty anyway.

For the performances maybe you're right. But how it's possible the mounting the same ext4 filesystem on 10 nodes at the same time without corruption? It does not have any logic for me...

I don't think that my customers SQL servers would very happy. The performances are almost acceptables with 4 path iscsi multipath yet. And live migration will continue to work? It won't lock the whole ext4 filesystem on a single cluster node? Or worst it won't corrupt the ext4 filesystem with...

Proxmox use the -T option by default when create a new virtual disk or new pool? In short words, proxmox uses thin volumes by default?

I think that many users have this bug but they haven't experienced yet becouse they don't have already deleted a file on the filesystem! I've ran my cluster almost for a month with this bug without issues just becouse I haven't deleted any file in this time. It's a very dangerous situation that...

For Two main reasons: 1. LVM on iSCSI doesn't support multipath. This is very important for us even for load balancing or fallback purposes. 2. Most important, LVM doesn't allow to overcommit the storage. Let me explain this. In one of our clusters we have almost 200 VMs where many of those...

Could be fine. But it's a production server and we won't upgrade to an unstable solution. We will wait for an updated and patched solution with stable 2.6 kernel. Until then we will use the 2.6.32-29 kernel. I've almost lost 10 Tbyte of customers data cause of it. Thankfully there is the live...

glad to hear it. Two weeks ago I opened a thread for the same problem without a solution: http://forum.proxmox.com/threads/22725-Bug-in-GFS2-Support-in-2-6-32-39-pve

I can't choose another filesystem. It would be great but there aren't other usable options. Ocfs2 it's deprecated and not supported by proxmox kernels. Gfs2 it's the only option for a one-block-device clustered filesystem. Multipath iscsi it's a non sacrificable option for us.

It'is a recent installation and it was the only other kernel installed. As described in the previous posts, as far i know the issue it's present in the latest enterprise kernel. I don't know if other versions are affected.

No sir. I've downgraded to the previous kernel to have an usble filesystem.

root@VMFO07:~# pveversion -v proxmox-ve-2.6.32: 3.4-157 (running kernel: 2.6.32-26-pve) pve-manager: 3.4-6 (running version: 3.4-6/102d4547) pve-kernel-2.6.32-39-pve: 2.6.32-157 pve-kernel-2.6.32-26-pve: 2.6.32-114 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve: 1.1.4-3...

2 K euros/year in community licenses and no answers in 4 days. Not even to confirm or deny the bug. Great service.

There is still a huge bug with the latest kernels: http://forum.proxmox.com/threads/22901-BUG-GFS2-Issue-Kernel-Panic-when-delete-on-a-new-fresh-filesystem

I can't belive that i'm the only one with this issue...

UPDATE: The bug it's kernel related. If i boot with 2.6.32-26-pve the issue isn't there: root@VMFO07:~# uname -a Linux VMFO07 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 x86_64 GNU/Linux root@VMFO07:~# multipath -ll [snip] dm-0 HP,MSA 1040 SAN size=9.1T features='0' hwhandler='0' wp=rw...

Hello everyone. We are using the enterprise repo on a 10-node cluster running Proxmox 3.4 (latest version). We're actually experiencing a strange behaviour with GFS2. We're trying to use GFS2 but with a new and clean filesystem we receive a kernel panic when trying to delete some file. Step by...

There is a serious bug in this release. Please wait for next kernel release: http://forum.proxmox.com/threads/22725-Bug-in-GFS2-Support-in-2-6-32-39-pve

Hello, we have a 10 node setup with a shared GFS2 Storage (we have used the gfs2-utils in the enterprise repo) and kernel 2.6.32-39-pve Since our latest upgrate to Proxmox 3.4, we're actually experiencing a serious bug already recognized by RedHat...

Just a note. The bridge it's configured with those options: auto vmbr0 iface vmbr0 inet manual bridge_ports eth1 bridge_stp off bridge_fd 0 bridge_maxwait 0 bridge_ageing 0