Separate names with a comma.
I done this many times, e.g. migrating VMs to a NFS-Storage and after that to another host. And this while the vm is running.
It is possible. Go to hardware, virtual disk, move to another storage, done.
...but not HA and not multiple disks at the same time
I always prefer LSI controllers with 1GB ram and BBU. But you get also good fsyncs with cheaper adaptec controllers with 512MB ram.
believe me...last week i did my 25th proxmox installation in production...and i testet zfs a lot...always gone back to hardware raid or san on lvm
Hi ZFS will not help you. You should use a Raid-Controller with writeback-cache and everything is fine with the fsyncs.
thank you Udo.
Any news to this ?...I have 2 clusters 3.4 with drbd dual primary...could I upgrade sometime safely?
simply install the headers.
apt-get install pve-headers-4.2.x.x
thank you so much...this saves my day...would be great if someone is testing this...I do not have the test hardware at the moment.
you did many posts so I thought you could be member of the team :)
So I should compile the DRDB 8.4 module myself like I did earlier...
you the proxmox team :)
But alright, thanks for the answer.
Perhaps you could provide a pve-kernel-4.2.2 with drbd 8.4 modules in it?
So no inplace upgrade though the DRBD9 Module is in the Kernel?
could someone tell me if I could upgrade my PM 3.4 Cluster with 3 nodes and 2 of them DRBD without any hassle?
I never had issues like this since I changed my VM-Cache Mode to writethrough.
interessted in this, too.
I have the same kind of problem. But my guest FS is BTRFS. It was an read error on vda1 but BTRFS self healing features read it from...
I think this helps:
maybe can you try to add in your vmid.conf
Nope sorry, I already tried that :)
i shouted out too early :) still had oos´s but the resync is fine after reboot. what about drbd9 any experiences yet ?