[DRBD-user] Inconsistent primary and UpToDate Secondary

Kushnir, Michael (NIH/NLM/LHC) [C] michael.kushnir at nih.gov
Thu May 28 18:00:40 CEST 2015

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


I have an interesting situation that I am not sure how to fix:

>From /var/log/messages:

May 27 09:09:55 XXXXX kernel: block drbd0: local READ IO error sector 8176113434+256 on sda1
May 27 09:09:55 XXXXX kernel: block drbd0: Local IO failed in __req_mod.
May 27 09:09:55 XXXXX kernel: block drbd0: disk( UpToDate -> Inconsistent )
>From /etc/init.d/drbd status:

drbd driver loaded OK; device status:
version: 8.4.5 (api:1/proto:86-101)
GIT-hash: 1d360bde0e095d495786eaeb2a1ac76888e4db96 build by phil at Build64R6, 2014-10-28 10:32:53
m:res  cs         ro                 ds                     p  mounted  fstype
0:r0   Connected  Primary/Secondary  Inconsistent/UpToDate  C

Primary is mounted and shared out over NFS. NFS share is taking reads and writes. MegaCLI reports no RAID or disk errors.

Is the primary reading and writing form the secondary at this point?

What is the best course of action to correct the situation?

Is the secondary truly up to date, or should I force a resync from the active primary?



Thanks,
Michael




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20150528/36decfcf/attachment.htm>


More information about the drbd-user mailing list