Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, after a damage of RAM on the second node I cannot re-use the second of two DRBD-resources: root at xen09:# drbdadm up drbd1_2 root at xen09:# cat /proc/drbd version: 8.3.7 (api:88/proto:86-91) srcversion: EE47D8BF18AC166BE219757 1: cs:WFConnection ro:Primary/Unknown ds:UpToDate/Outdated C r---- ns:0 nr:0 dw:0 dr:200 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos: 1424 2: 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 root at xen09:# drbdadm primary drbd1_2 2: State change failed: (-2) Refusing to be Primary without at least one UpToDate disk Command 'drbdsetup 2 primary' terminated with exit code 17 root at xen09:# drbdadm down drbd1_2 root at xen09:# drbdadm create-md drbd1_2 md_offset 1073737728 al_offset 1073704960 bm_offset 1073672192 Found swap space signature 1048508 kB left usable by current configuration Device size would be truncated, which would corrupt data and result in 'access beyond end of device' errors. If you want me to do this, you need to zero out the first part of the device (destroy the content). You should be very sure that you mean it. Operation refused. Command 'drbdmeta 2 v08 /dev/vg1/lv_drbd1_2 internal create-md' terminated with exit code 40 drbdadm create-md drbd1_2: exited with code 40 -------------------- What can I do in such a situation? The work-around will be: don't use DRBD for DomU-swap, don't use Primary/Primary, don't use live-migration ... Helmut Wollmersdorfer