[DRBD-user] Nonsense refusal

Florian Haas f.g.haas at gmx.net
Sun Sep 11 21:57:49 CEST 2011

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On 2011-09-11 21:52, Nick Khamis wrote:
> root at mydrbd1:/# drbdadm disconnect r0.res
> 0: State change failed: (-2) Refusing to be Primary without at least
> one UpToDate disk
> Command 'drbdsetup 0 disconnect' terminated with exit code 17
> root at mydrbd1:/# /etc/init.d/drbd status
> drbd driver loaded OK; device status:
> version: 8.3.7 (api:88/proto:86-91)
> srcversion: EE47D8BF18AC166BE219757
> m:res     cs         ro                 ds                 p  mounted   fstype
> 0:r0_res  Connected  Primary/Secondary  Diskless/UpToDate  C  /service  ext3
> I am not asking it to be primary. FYI drbdadm primary r0.res on the
> same node works fine.

You're detached from local storage (Diskless). DRBD is currently serving
all of its data over the wire from the good, UpToDate node. You are
asking DRBD to disconnect from its peer data while keeping it Primary.
In effect, you're asking DRBD to continue to serve data, hence pulling
the latter out of thin air.

DRBD is not the Fed. It can't create something useful out of nothing.

Now, if you want to disconnect, you'll have to either demote (make the
local DRBD instance Secondary), or attach (connect to a valid backing
device) again, and wait for the resync to complete.

Hope this helps.


More information about the drbd-user mailing list