Recent content by Black Knight MHT

Hi. We have 3 nodes HA cluster. 2 nodes (pve2/3) have drbd9 storage + 1 (pve1) node for Quorum. pve2/3 - HP 380G6/7 pve1 - Dell 2950 Network: PVE3 -- (LACP 4*1G) -- Cisco 7604 -- (LACP 2*10G) -- Extreme 650-24x -- (10G) - PVE2 Extreme 650-24x -- (2*10G) -- Dlink 3620 -- (LACp 2*1G) -- PVE1...

And what about nearest future? Will I able to setup another nod with this software? DRBD9 is very comfortable.....

Hi! As I could understand.....if i use DRBD9 now and upgrade my nodes to the latest version - DRBD will be broken!?!

Hi. It's strange, but after upgrading nodes to pve-manager/4.3-10/7230e60f (running kernel: 4.4.19-1-pve), there is no problems with movement.

Sorry....but I had no time to check and dig deeper the problem with mysql....and restore from backup (((((((( I'll try to make more tests tomorrow on the test Cluster.

Ok, people. Let's live in peace. There is nobody "clever than anyone else in the universe"....we simply have some troubles with function of moving disk. And I try to understand is it safety use it. Anybody knows how it work with cache (raid, disk, host-system, VM)? And why it is only with mysql...

In progress.....on "hot" cluster don't want make tests, so installing another cluster for tests. Yes one by one......non-multiple movement Yes to all.....also there are hardware controllers with BBU and cache No errors on network..... It's strange that all other VM's without MySQL moved...

May I join you conversation..... We have PVE cluster with 3 nodes (All of them 4.3-3), and use NFS Share based on FreeNAS. Not so far we opened to ourselves "move disks".......It was very cool....and gives us opportunity migrate VM from one storage to another without "backup/restore". For a...

Hi! I think that I have the same bug..... Will fix need rebooting or re-installing the node? I have 3 nodes....2 of them were installed from 4.0 iso..and updated to 4.3-3..and there is lsblk: root@pve3:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 820.2G 0 disk ├─sda1 8:1 0...

Well. I've done tests myself. a) Fail of hdd (in my situation it was raid0 of 2*300Gb sas 15K drives) on pve5 and vm id 550 On working node: 1. drbdmanage unassign vm-550-disk-1 pve5 2. drbdmanage delete-node -f pve5 On fail node: 1. replace fail drives 2. parted /dev/sda mktable gpt 3. parted...

ОК....And what about adding 3 node after creating VM in PVE? Did You do failover test with HDD?

I guess you are trying to setup drbd8.......that isn't support in PVE4........You need DRBD9 https://pve.proxmox.com/wiki/DRBD9

I have seen this warning...BUT!....it works without drbdmanage.cfg)))))) I don't know how?!?! It was some troubles with changing name of lvs. Try default schema.

Well. I have success with: 1. install version 0.97-1 2. init (already 3 nodes) all nodes 3. add-node from master. 4. update to the latest version root@pve4:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 279.4G 0 disk ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 127M 0 part...

Hi! Try method 1......but del drbdmanager first