[DRBD-user] [CASE-21] On V9.0.1-1, after resync disk status is Outdated sometimes.

김재헌 jhkim at mantech.co.kr
Wed Feb 17 09:23:46 CET 2016

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 resync, disk status is "Outdated" sometimes.

1. drbd.conf

 -  we configure 5 nodes but use only 3 nodes on test.

[root at drbd9-01 ~]# drbdadm dump r0
# resource r0 on drbd9-01: not ignored, not stacked
# defined at /etc/drbd.d/r0.res:1
resource r0 {
    device               /dev/drbd1 minor 1;
    meta-disk            internal;
    on drbd9-01 {
        node-id 0;
        address          ipv4 100.100.10.11:7000;
    }
    on drbd9-02 {
        node-id 1;
        address          ipv4 100.100.10.21:7000;
    }
    on drbd9-03 {
        node-id 2;
        address          ipv4 100.100.10.31:7000;
    }
    on drbd9-04 {
        node-id 3;
        address          ipv4 100.100.10.41:7000;
    }
    on drbd9-05 {
        node-id 4;
        address          ipv4 100.100.10.51:7000;
    }
    connection-mesh {
        hosts drbd9-01 drbd9-02 drbd9-03 drbd9-04 drbd9-05;
    }
}



2. Version

[root at drbd9-01 ~]# cat /proc/drbd
version: 9.0.1-1 (api:2/proto:86-111)
GIT-hash: f57acfc22d29a95697e683fb6bbacd9a1ad4348e build by root at drbd9-01,
2016-02-16 17:26:06



3. Test
 - 1) drbd up on 3 nodes
 - 2) fullsync



4. Status/Logs

 1) Node1

[root at drbd9-01 ~]# drbdadm primary --force r0
[root at drbd9-01 ~]# drbdadm status r0
r0 role:Primary
  disk:UpToDate
  drbd9-02 role:Secondary
    replication:SyncSource peer-disk:Inconsistent done:0.02
  drbd9-03 role:Secondary
    replication:SyncSource peer-disk:Inconsistent done:0.02
  drbd9-04 connection:Connecting
  drbd9-05 connection:Connecting


  11109 Feb 17 16:09:56 drbd9-01 kernel: drbd r0/0 drbd1 drbd9-02: Resync
done (total 122 sec; paused 0 sec; 40968 K/sec)
  11110 Feb 17 16:09:56 drbd9-01 kernel: drbd r0/0 drbd1 drbd9-02: pdsk(
Inconsistent -> UpToDate ) repl( SyncSource -> Established )
  11111 Feb 17 16:09:57 drbd9-01 kernel: drbd r0/0 drbd1 drbd9-03: Resync
done (total 123 sec; paused 0 sec; 40636 K/sec)
  11112 Feb 17 16:09:57 drbd9-01 kernel: drbd r0/0 drbd1 drbd9-03: pdsk(
Inconsistent -> UpToDate ) repl( SyncSource -> Established )
  11113 Feb 17 16:10:00 drbd9-01 dbus-daemon: dbus[928]: [system]
Activating service name='org.freedesktop.PackageKit' (using servicehelper
     )


 2) Node2

[root at drbd9-02 ~]# drbdadm status r0
r0 role:Secondary
  disk:UpToDate
  drbd9-01 role:Primary
    peer-disk:UpToDate
  drbd9-03 role:Secondary
    peer-disk:UpToDate
  drbd9-04 connection:Connecting
  drbd9-05 connection:Connecting


Feb 17 16:09:56 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-01: updated UUIDs
B6CAADFB7D215BC6:0000000000000000:0000000000000000:0000000000000000
Feb 17 16:09:56 drbd9-02 kernel: drbd r0/0 drbd1: disk( Inconsistent ->
UpToDate )
Feb 17 16:09:56 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-05: pdsk( DUnknown
-> Outdated ) resync-susp( connection dependency -> no )
Feb 17 16:09:56 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-04: pdsk( DUnknown
-> Outdated ) resync-susp( connection dependency -> no )
Feb 17 16:09:56 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-01: repl( SyncTarget
-> Established )
Feb 17 16:09:56 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-01: helper command:
/sbin/drbdadm after-resync-target
Feb 17 16:09:56 drbd9-02 drbdadm[4714]: Don't know which config file
belongs to resource r0, trying default ones...
Feb 17 16:09:56 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-01: helper command:
/sbin/drbdadm after-resync-target exit code 0 (0x0)
Feb 17 16:09:57 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-03: updated UUIDs
B6CAADFB7D215BC6:0000000000000000:0000000000000000:0000000000000000
Feb 17 16:09:57 drbd9-02 kernel: drbd r0/0 drbd1 drbd9-03: pdsk(
Inconsistent -> UpToDate ) resync-susp( peer -> no )


 3) Node3

[root at drbd9-03 etc]# drbdadm status r0
r0 role:Secondary
  disk:UpToDate
  drbd9-01 role:Primary
    peer-disk:UpToDate
  drbd9-02 role:Secondary
    peer-disk:Outdated <-----------------------------------------
Why??????????
  drbd9-04 connection:Connecting
  drbd9-05 connection:Connecting


Feb 17 16:09:56 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-02: pdsk(
Inconsistent -> UpToDate )
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-01: Resync done
(total 123 sec; paused 0 sec; 40636 K/sec)
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-01: updated UUIDs
B6CAADFB7D215BC6:0000000000000000:0000000000000000:0000000000000000
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1: disk( Inconsistent ->
UpToDate )
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-05: pdsk( DUnknown
-> Outdated ) resync-susp( connection dependency -> no )
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-04: pdsk( DUnknown
-> Outdated ) resync-susp( connection dependency -> no )
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-02: pdsk( UpToDate
-> Outdated ) resync-susp( connection dependency -> no )
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-01: repl( SyncTarget
-> Established )
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-01: helper command:
/sbin/drbdadm after-resync-target
Feb 17 16:09:57 drbd9-03 kernel: drbd r0/0 drbd1 drbd9-01: helper command:
/sbin/drbdadm after-resync-target exit code 0 (0x0)



5. Question
 - If we do disconnect and connect again on the Node3, the status becomes
UpToDate.

[root at drbd9-03 drbd-utils-8.9.6]# drbdadm status r0
r0 role:Secondary
  disk:UpToDate
  drbd9-01 role:Primary
    peer-disk:UpToDate
  drbd9-02 role:Secondary
    peer-disk:UpToDate <--------------------------- Changed to Normal!!!!
  drbd9-04 connection:Connecting
  drbd9-05 connection:Connecting

 - Why did the node3 become Outdated after resync despite of normal?


Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160217/baea131c/attachment.htm>


More information about the drbd-user mailing list