dbarker at visioncomm
Aug 16, 2012, 3:55 PM
Post #2 of 2
Run a verify. It will show issues, I imagine. The version "you like" should
be primary. drbdadm disconnect and then drbdadm connect (from either node)
and they'll sync up.
I imagine some changes were made to one of the devices while not under drbd
control, so no "stale" bits were set in the bitmap. Verify will find them
all and update the bitmap.
Also, be CERTAIN you are not mounting the underlying block devices not via
drbd anywhere, ever.
Oops, I just reread your message, "The systems have been synced twice". How
are you performing the sync? The verify/disconnect/reconnect is the
fastest/best way to resync nearly identical resources. If you have truly
synced the devices and not written to them outside drbd control, the only
way they can diverge is hardware failure - rarely undetected.
Good luck. Let us know how it goes!
From: drbd-user-bounces [at] lists
[mailto:drbd-user-bounces [at] lists] On Behalf Of Two Spirit
Sent: Saturday, August 04, 2012 11:14 AM
To: drbd-user [at] lists
Subject: [DRBD-user] ds:Uptodate not uptodate
Hi, newbie here,
I'm trying to figure out what is going on. I've got 2 servers,
primary/secondary, disk states are both uptodate,
but there is different information on both on both servers.
If I make server1 the primary and mount it, I find file1 in the file system.
if I make server1 the secondary and server2 the primary, I find file2 in the
filesystem, but not file1.
The systems have been synced twice. Not sure how to proceed to figure this