On 01/06/16 11:44, For@ll wrote:
Effect is the same
drbdadm -- -o primary r2
2: State change failed: (-2) Refusing to be Primary without at least one
UpToDate disk
Command 'drbdsetup 2 primary -o' terminated with exit code 17
Try upgrading . . .
From the ChangeLog, version 8.3.8 fixed f
W dniu 01.06.2016 o 12:39, Simon Ironside pisze:
On 01/06/16 11:14, For@ll wrote:
cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
srcversion: EE47D8BF18AC166BE219757
0: cs:WFConnection ro:Secondary/Unknown ds:Consistent/DUnknown C r
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
On 01/06/16 11:14, For@ll wrote:
cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
srcversion: EE47D8BF18AC166BE219757
0: cs:WFConnection ro:Secondary/Unknown ds:Consistent/DUnknown C r
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
1: cs:WFConnection ro:Secondary/U
Hi,
Yesterday my primary server crash and now I want start my services on
the second server, but my drbd disks has status:
cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
srcversion: EE47D8BF18AC166BE219757
0: cs:WFConnection ro:Secondary/Unknown ds:Consistent/DUnknown C r
ns:0 nr:
Hi to all
- I would like to know which is the more secure algorithm for the online
device verification?
- Also i would like to know if we have a tie in the first place (acording to
the first question), which is the more quick?
Best regards
Cesar
