LINUX.ORG.RU
ФорумAdmin

Proxmox 4.3 + DRBD9

 ,


0

1

Делал по этому мануалу https://pve.proxmox.com/wiki/DRBD9

При добавлении нод получал такой выхлоп:

root@node01:~# drbdmanage add-node -q node02 10.0.1.2
WARNING:root:Could not read configuration file '/etc/drbdmanaged.cfg'
Operation completed successfully
Operation completed successfully

Executing join command using ssh.
IMPORTANT: The output you see comes from node02
IMPORTANT: Your input is executed on node02
WARNING:root:Could not read configuration file '/etc/drbdmanaged.cfg'
Error: Operation not allowed on satellite node

Всего 3 ноды

Кстати что означет ключ "-q"?

В итоге получаю вот что:

root@node01:~# drbdmanage list-nodes
WARNING:root:Could not read configuration file '/etc/drbdmanaged.cfg'
+---------------------------------------------------------------------------------------+
| Name   | Pool Size | Pool Free |       |                                        State |
|---------------------------------------------------------------------------------------|
| node01 |      9216 |      9216 |       |                                           ok |
| node02 |   unknown |   unknown |       | OFFLINE, pending actions: adjust connections |
| node03 |   unknown |   unknown |       | OFFLINE, pending actions: adjust connections |
+---------------------------------------------------------------------------------------+

До кучи:

root@node01:~# pvs
  PV         VG       Fmt  Attr PSize  PFree  
  /dev/sda3  pve      lvm2 a--   7.87g 876.00m
  /dev/sdb1  drbdpool lvm2 a--  10.00g 860.00m

root@node01:~# drbd-overview
 0:.drbdctrl/0  Conn(node01)/C'ng(node03,node02) Seco(node01)/Unkn(node03,node02) UpTo(node01)/DUnk(node02,node03) 
 1:.drbdctrl/1  Conn(node01)/C'ng(node02,node03) Seco(node01)/Unkn(node03,node02) UpTo(node01)/DUnk(node03,node02)

root@node01:~# lsblk
NAME                            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                               8:0    0    8G  0 disk 
├─sda1                            8:1    0 1007K  0 part 
├─sda2                            8:2    0  127M  0 part 
└─sda3                            8:3    0  7.9G  0 part 
  ├─pve-root                    251:0    0  1.8G  0 lvm  /
  ├─pve-swap                    251:7    0  896M  0 lvm  [SWAP]
  ├─pve-data_tmeta              251:8    0    8M  0 lvm  
  │ └─pve-data                  251:10   0  4.4G  0 lvm  
  └─pve-data_tdata              251:9    0  4.4G  0 lvm  
    └─pve-data                  251:10   0  4.4G  0 lvm  
sdb                               8:16   0   10G  0 disk 
└─sdb1                            8:17   0   10G  0 part 
  ├─drbdpool-lvol0              251:1    0  128M  0 lvm  
  ├─drbdpool-drbdthinpool_tmeta 251:2    0   12M  0 lvm  
  │ └─drbdpool-drbdthinpool     251:4    0    9G  0 lvm  
  ├─drbdpool-drbdthinpool_tdata 251:3    0    9G  0 lvm  
  │ └─drbdpool-drbdthinpool     251:4    0    9G  0 lvm  
  ├─drbdpool-.drbdctrl_0        251:5    0    4M  0 lvm  
  │ └─drbd0                     147:0    0    4M  1 disk 
  └─drbdpool-.drbdctrl_1        251:6    0    4M  0 lvm  
    └─drbd1                     147:1    0    4M  1 disk 
sr0                              11:0    1 1024M  0 rom

root@node01:~# drbdadm status
.drbdctrl role:Secondary
  volume:0 disk:UpToDate
  volume:1 disk:UpToDate
  node02 connection:Connecting
  node03 connection:Connecting

 



Последнее исправление: alexanderg (всего исправлений: 2)
Ответ на: комментарий от Davyd
basically we do not want that others (who have not contributed to the
development) act as parasites in our support business
So we are basically forced to remove the package from our repository. We will
also remove the included storage driver to make sure that we and our
customers do not violate that license.

Please contact Linbit if you want to use drbdmanage/DRBD9 in future. They may
provide all necessary packages.
alexanderg
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.