[DRBD-user] problem with partially Outofdate .drbdctrl resource

Arnold Veenema arnold at veenema.net
Mon Apr 30 11:11:20 CEST 2018


Greetings,

I've got this situation where 1 of the volumes of the .drbdctrl resource is
Outofdate.
Forcing the resource to primary is not allowed for just the
Outofdate-volume as the command is only working for a complete resource...
How do I solve this partially Outofdate state?

root at NODE01:~# drbdadm status
.drbdctrl role:Primary
  volume:0 disk:UpToDate
  volume:1 disk:Outdated
  NODE02 role:Secondary
    volume:0 peer-disk:UpToDate
    volume:1 peer-disk:Outdated

some-db-data role:Primary
  disk:UpToDate
  NODES02 role:Secondary
    peer-disk:UpToDate

some-more-db-data role:Primary
  disk:UpToDate
  NODE02 role:Secondary
    peer-disk:UpToDate

root at NODE01:~# drbdadm --version
DRBDADM_BUILDTAG=GIT-hash:\ 9a59335e72cb374d1c624df466012efb8e3d6aec\
build\ by\ buildd at lgw01-amd64-014\,\ 2018-03-21\ 09:47:09
DRBDADM_API_VERSION=2
DRBD_KERNEL_VERSION_CODE=0x09000c
DRBD_KERNEL_VERSION=9.0.12
DRBDADM_VERSION_CODE=0x090300
DRBDADM_VERSION=9.3.0

root at NODE01:~# drbdadm -- --overwrite-data-of-peer primary .drbdctrl/1
primary operates on whole resources, but you specified a specific volume!


Met vriendelijke groet / Regards,
Arnold Veenema
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20180430/58d6e391/attachment.htm>


More information about the drbd-user mailing list