Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DRBD: Users

Problem with creating

 

 

DRBD users RSS feed   Index | Next | Previous | View Threaded


mensagens at marcelofrota

Apr 20, 2012, 1:52 PM

Post #1 of 3 (734 views)
Permalink
Problem with creating

Dears,
I use drbd in two machines connected



I
executed the comands in second node :

modprobe drbd
/sbin/drbdadm create-md
partition4
/sbin/drbdadm up partition4

In primary node i
executed :
modprobe drbd
/sbin/drbdadm create-md
partition4
/sbin/drbdadm up partition4
/sbin/drbdadm --
--overwrite-data-of-peer primary partition4
mkfs /dev/drbd0

In
/var/log/syslog
The log show:



Executing '/sbin/drbdadm --
--overwrite-data-of-peer primary partition4'
kernel: [ 1351.610443] block
drbd4: Not fencing peer, I'm not even Consistent myself.
kernel: [ 1351.610447] block
drbd4: Forced into split brain situation!
kernel: [ 1351.610453] block
drbd4: role( Secondary -> Primary ) disk( Inconsistent ->
UpToDate ) pdsk( DUnknown -> Outdated )

kernel: [ 1351.611116] block
drbd4: Forced to consider local data as UpToDate!
kernel: [ 1351.611148] block
drbd4: new current UUID
C591FBC821A81D4B:0000000000000004:0000000000000000:0000000000000000

Anyone
seen this problem in the log? can you help me?



My global_common.conf :




global {

usage-count yes;

}


common {

protocol B;


syncer {

rate 100M;

al-extents 3389;

}


handlers {

outdate-peer
"/usr/lib/heartbeat/drbd-peer-outdater";

split-brain
"/usr/lib/drbd/notify-split-brain.sh root";

}


disk {

on-io-error detach;

fencing resource-only;

}


net {

after-sb-0pri
discard-zero-changes;

after-sb-1pri discard-secondary;

after-sb-2pri disconnect;

max-buffers 8000;

max-epoch-size 8000;

sndbuf-size 0;

}

}



Best reguards,
Marcelo Frota


dirk at proactive

Apr 21, 2012, 2:28 AM

Post #2 of 3 (702 views)
Permalink
Re: Problem with creating [In reply to]

Hi,

Normally, you would do your 'mkfs' after you initialized the drbd disks.

Did the synchronisation run after your 'drbdadm --
--overwrite-data-of-peer primary' command?

It should have, the log messages:

kernel: [ 1351.610453] block drbd4: role( Secondary -> Primary ) disk(
Inconsistent -> UpToDate ) pdsk( DUnknown -> Outdated )

kernel: [ 1351.611116] block drbd4: Forced to consider local data as
UpToDate!


Are normal after a 'drbdadm -- --overwrite-data-of-peer primary'.

Cheers,

Dirk

Op 20-4-2012 22:52, mensagens [at] marcelofrota schreef:
> Dears,
>
> I use drbd in two machines connected
>
>
> I executed the comands in second node :
> modprobe drbd
> /sbin/drbdadm create-md partition4
> /sbin/drbdadm up partition4
>
> In primary node i executed :
> modprobe drbd
> /sbin/drbdadm create-md partition4
> /sbin/drbdadm up partition4
>
> /sbin/
>
> kernel: [ 1351.610453] block drbd4: role( Secondary -> Primary ) disk(
> Inconsistent -> UpToDate ) pdsk( DUnknown -> Outdated )
>
> kernel: [ 1351.611116] block drbd4: Forced to consider local data as
> UpToDate!
>
> mkfs /dev/drbd0
>
> In /var/log/syslog
> The log show:
>
> Executing '/sbin/drbdadm -- --overwrite-data-of-peer primary partition4'
>
> kernel: [ 1351.610443] block drbd4: Not fencing peer, I'm not even
> Consistent myself.
>
> kernel: [ 1351.610447] block drbd4: Forced into split brain situation!
>
> kernel: [ 1351.610453] block drbd4: role( Secondary -> Primary ) disk(
> Inconsistent -> UpToDate ) pdsk( DUnknown -> Outdated )
>
> kernel: [ 1351.611116] block drbd4: Forced to consider local data as
> UpToDate!
>
> kernel: [ 1351.611148] block drbd4: new current UUID
> C591FBC821A81D4B:0000000000000004:0000000000000000:0000000000000000
>
>
> Anyone seen this problem in the log? can you help me?
>
>
> My global_common.conf :
>
>
> global {
>
> usage-count yes;
>
> }
>
> common {
>
> protocol B;
>
> syncer {
>
> rate 100M;
>
> al-extents 3389;
>
> }
>
> handlers {
>
> outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater";
>
> split-brain "/usr/lib/drbd/notify-split-brain.sh root";
>
> }
>
> disk {
>
> on-io-error detach;
>
> fencing resource-only;
>
> }
>
> net {
>
> after-sb-0pri discard-zero-changes;
>
> after-sb-1pri discard-secondary;
>
> after-sb-2pri disconnect;
>
> max-buffers 8000;
>
> max-epoch-size 8000;
>
> sndbuf-size 0;
>
> }
>
> }
>
>
> Best reguards,
> Marcelo Frota
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user

--
<http://www.proactive.nl>
T 023 - 5422299
F 023 - 5422728

www.proactive.nl <http://www.proactive.nl>
Attachments: signature.gif (3.87 KB)


lists at alteeve

Apr 21, 2012, 9:21 AM

Post #3 of 3 (702 views)
Permalink
Re: Problem with creating [In reply to]

It looks like you have a network problem.

1. What is the resource configuration?
2. What is your network configuration?

Now that you've got a split-brain, you will need to repair that before
you can try to connect them again. Is this ver. 8.3.x?

http://www.drbd.org/users-guide/s-resolve-split-brain.html

Once cleared up, on each node try;

modprobe drbd
drbdadm attach <res>
drdbadm connect <res>

Then 'cat /proc/drbd' and see what it says. If it's still showing
'StandAlone', then it detected a split-brain again. If both show
'WFConnection', then your network issue has not been resolved.

Digimer

On 04/20/2012 04:52 PM, mensagens [at] marcelofrota wrote:
> Dears,
>
> I use drbd in two machines connected
>
>
> I executed the comands in second node :
> modprobe drbd
> /sbin/drbdadm create-md partition4
> /sbin/drbdadm up partition4
>
> In primary node i executed :
> modprobe drbd
> /sbin/drbdadm create-md partition4
> /sbin/drbdadm up partition4
>
> /sbin/drbdadm -- --overwrite-data-of-peer primary partition4
>
> mkfs /dev/drbd0
>
> In /var/log/syslog
> The log show:
>
> Executing '/sbin/drbdadm -- --overwrite-data-of-peer primary partition4'
>
> kernel: [ 1351.610443] block drbd4: Not fencing peer, I'm not even
> Consistent myself.
>
> kernel: [ 1351.610447] block drbd4: Forced into split brain situation!
>
> kernel: [ 1351.610453] block drbd4: role( Secondary -> Primary ) disk(
> Inconsistent -> UpToDate ) pdsk( DUnknown -> Outdated )
>
> kernel: [ 1351.611116] block drbd4: Forced to consider local data as
> UpToDate!
>
> kernel: [ 1351.611148] block drbd4: new current UUID
> C591FBC821A81D4B:0000000000000004:0000000000000000:0000000000000000
>
>
> Anyone seen this problem in the log? can you help me?
>
>
> My global_common.conf :
>
>
> global {
>
> usage-count yes;
>
> }
>
> common {
>
> protocol B;
>
> syncer {
>
> rate 100M;
>
> al-extents 3389;
>
> }
>
> handlers {
>
> outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater";
>
> split-brain "/usr/lib/drbd/notify-split-brain.sh root";
>
> }
>
> disk {
>
> on-io-error detach;
>
> fencing resource-only;
>
> }
>
> net {
>
> after-sb-0pri discard-zero-changes;
>
> after-sb-1pri discard-secondary;
>
> after-sb-2pri disconnect;
>
> max-buffers 8000;
>
> max-epoch-size 8000;
>
> sndbuf-size 0;
>
> }
>
> }
>
>
> Best reguards,
> Marcelo Frota
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user


--
Digimer
Papers and Projects: https://alteeve.com
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

DRBD users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.