Hi all,
Back in 2010, we deployed a small infrastructure based on drbd and
ocfs2. All was working fine excepted that time to time checksumming
detect that data were altered between the two nodes (more information
here
http://thread.gmane.org/gmane.linux.network.drbd/20425/focus=20432). As
On 20/06/13 17:51, Paul O'Rorke wrote:
Does anyone have any thoughts on why my data doesn't seem to be
replicating or perhaps point me in the right direction for how to dig a
little deeper. My limited understanding is that DRBD should be between
my host and the LVM volume but perhaps it's
Hello,
I already faced this issue sporadically a few months ago, it occured again last
night.
Here is what happens.
Online verification is running (as a weekly basis) :
root@srv2-1:~# cat /proc/drbd
version: 8.3.15 (api:88/proto:86-97)
GIT-hash: 0ce4d235fc02b5c53c1c52c53433d11a694eab8c
Simon,
thank you so much. I saw a reference to that on the pages about xen and
should have realized it would apply to any virtual environment. Doh!
Writing to /dev/drbd/by-res/r1 did it and I now have my first vm ticking
along nicely through DRBD and I'm a very happy camper.
Thanks again
Dear readers
I have configured drbd with resource syncer
Since everything is running fine, the command
#drbdadm verify resource
outputs nothing
I'm wondering what the output could be if some re-sync is needed, this is
meant to use it with cron.
Thank you for hinting
Roberto
On 20/06/13 23:56, Roberto Fastec wrote:
I'm wondering what the output could be if some re-sync is needed, this
is meant to use it with cron.
Have a look at /proc/drbd.
The bit you're interested in is the oos: part for the resource you're
verifying. If the verify discovered out of sync
Le 21 juin 2013 à 02:41, Simon Ironside a écrit :
On 20/06/13 23:56, Roberto Fastec wrote:
I'm wondering what the output could be if some re-sync is needed, this
is meant to use it with cron.
Have a look at /proc/drbd.
The bit you're interested in is the oos: part for the resource
