gmane.comp.linux.drbd

Rescue after reduce :(

Christian Völker — 2012-05-25T06:32:02

Hi,

I've a drbd device (8.3) on both sides on aLVM volume.

I tried to reduce the device now. Steps I did:
- fsck -f (ext3)
- reduced filesystem to 1,400G
- drbdadm -- --new-size=1450G resize
- lvreduce drbdvol -L 1500G
- fsck -f 
- lvreduce on secondary

So far everything went fine. 

After mounting the device I got a corrupted filesystem  with i/o errors and both nodes are on "diskless".

I assume after the first lvreduce the primary was already on diskless but performed the fsck pn the secondarys disk (which was still on the larger old size)
Any clue how to recover?

And any hints how to perform the reduce properly?




Christian

leaked indexing text in users guide

Paul Theodoropoulos — 2012-05-24T20:16:27

http://www.drbd.org/users-guide/s-nested-lvm.html

    In order to enable this configuration, follow these steps:

      *

        Set an appropriate |filter| option in your |/etc/lvm/lvm.conf|:

        indexterm:[LVM]indexterm:[filter expression (LVM)]

    filter = ["a|sd.*|", "a|drbd.*|", "r|.*|"]


Just fyi.

re source Primary but inconsistent

envisionrx — 2012-05-24T17:05:57

I was creating a new resource on our servers and ended up in an interesting
state and I'm wondering if DRBD (8.3.12) just handles this correctly, or if
this is bad.

I created a stacked resource on server1, using steps like this:
1) created an lvm to back the resource lvcreate -n store1 -L 2048g backingvg
2) added the resource configuration to /etc/drbd.d directory for both the
lower and upper resources and copied the config to the other nodes.
3) ran drbdadm create-md on the lower resource: drbdadm create-md
store1_lower
4) brought up the lower device: drbdadm up store1_lower
5) made the resource primary: drbdsetup /dev/drbd1 primary -o
6) ran drbdadm create-md on the upper resource: drbdadm --stacked create-md
store1
7) brought up the upper resource: drbdadm up --stacked store1
8) made the upper resource primary: drbdsetup /dev/drbd11 primary -o
9) formatted the upper resource: mkfs.ext4 /dev/drbd11

It should be noted that all my other resources are primary on the other node
(server2), I thought it would be less risky to work on this on the
non-active node initially.  I used a different ip for the stacked ip than my
active nodes while configuring it on server1.  After getting the resource
formatted I stopped all the resources, edited the config to use the same ip
I use for the stacked ip on the rest of my resources and then just brought
up the lower resource and left it secondary.

next on server2 I did steps 1, 3 and 4 to bring up the resource and let it
start syncing.

So at this point i have the resource secondary/UpToDate on server1.  Then,
just to see if it would, I tried to make the resource primary on server2. 
To my surprise drbd happily made the resource primary on server2!  I didn't
issue the drbdsetup command that forces it primary as above, I only issued
the standard command: 
drbdadm primary storage1_lower 

Intrigued, I went ahead and brought up the upper resource and made it
primary also.  I then brought up the resource on the remote node (storage3)
and let it start syncing.

So, now i have the following:
server1:     1: cs:SyncSource ro:Secondary/Primary ds:UpToDate/Inconsistent
C r-----
server2:     1: cs:SyncTarget ro:Primary/Secondary ds:Inconsistent/UpToDate
C r-----
server2:    11: cs:SyncSource ro:Secondary/Secondary
ds:UpToDate/Inconsistent A r-----
server3:    11: cs:SyncTarget ro:Secondary/Secondary
ds:Inconsistent/UpToDate A r-----

So, my question is, did i just bork the resource totally and I should start
over, or is DRBD smart enough to handle this situation by grabbing data not
yet synced to server2 from server1 if it is accessed, and updating data on
server1 if it is written to the primary on server2?

I did make the upper resource primary and mounted it on server2, just to see
if I could, and it worked also.  Since the drive is empty all i could see
was the lost and found directory.

harddisk problems

Marcel Kraan — 2012-05-24T16:22:59

i have so much problems with my (virtual) disks.
i see articles from virtual box

ext4 and kvm going error?
i need to set the Host IO ?

But i don't understand?
Is there a solution?

2 x 
quad core super micro.
32GB 
RAID5 6TB (4TB)



Buffer I/O error on device sdc1, logical block 65273728
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273729
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273730
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273731
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273732
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273733
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273734
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273735
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273736
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273737
lost page write due to I/O error on sdc1
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.01: failed command: WRITE DMA EXT
ata2.01: cmd 35/00:00:3f:fc:cf/00:04:1f:00:00/f0 tag 0 dma 524288 out
         res 40/00:01:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
ata2.01: status: { DRDY }
ata2: soft resetting link
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: READ DMA
ata1.01: cmd c8/00:08:c7:10:68/00:00:00:00:00/f4 tag 0 dma 4096 in
         res 40/00:01:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
ata1.01: status: { DRDY }
ata1: soft resetting link
ata2.01: configured for MWDMA2
ata2.01: device reported invalid CHS sector 0
ata2: EH complete
ata1.00: configured for MWDMA2
ata1.01: configured for MWDMA2
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
sd 0:0:1:0: [sdb] Unhandled error code
sd 0:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
sd 0:0:1:0: [sdb] CDB: Read(10): 28 00 04 95 55 3f 00 01 00 00
ata2: lost interrupt (Status 0x50)
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
sd 1:0:1:0: [sdc] Unhandled error code
sd 1:0:1:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
sd 1:0:1:0: [sdc] CDB: Write(10): 2a 00 00 00 00 87 00 00 08 00
__ratelimit: 118 callbacks suppressed
Buffer I/O error on device sdc1, logical block 9
ata1.01: failed command: READ DMA EXT
ata1.01: cmd 25/00:00:67:e7:89/00:01:27:00:00/f0 tag 0 dma 131072 in
         res 40/00:01:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
ata1.01: status: { DRDY }
ata1: soft resetting link
lost page write due to I/O error on sdc1
ata1.00: configured for MWDMA2
ata1.01: configured for MWDMA2
ata1.01: device reported invalid CHS sector 0

DRBD initial settings for two disks

Tero Mäntyvaara — 2012-05-24T11:25:42

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi!

I was reading document
https://help.ubuntu.com/10.04/serverguide/drbd.html. Would the following
configuration be correct with two disks?

|/etc/drbd.conf|:
resource r0 {
  volume 0 {
    device    /dev/drbd1;
    disk      /dev/sdb1;
    meta-disk internal;
  }
  volume 1 {
    device    /dev/drbd2;
    disk      /dev/sdb2;
    meta-disk internal;
  }

  on drbd01 {
    address   192.168.0.1:7788;
  }
  on drbd02 {
    address   192.168.0.2:7788;
  }
}


Tero Mäntyvaara
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iQEcBAEBAgAGBQJPvhq1AAoJEHIK6cOQy5X4UtEIAL4cy0f8u40/Jf3hdsaV3aUX
KSpweN0hmcTYXKAhraJmR3PTSzuBG3fIF7FI6GaxVY9EcIsSolWbYW2wnNSS0kCV
inc9stT3J07sW5j5t6UvPg9LkI8+ptLv+WJfy1FEZCjVC2dMMK1gxzZf/Ha9+tj9
DC9g7V9bTZB1aDxS5U3r/R2NDKbKYKgsxaZYRHcFLwnh9zJNvbYtuy6tLQj8L7sf
Sma16/j4yEfOHXFbs8VZZR4kMo346G4pt7zD3UOY1b2ZNjHOVuA1oBF7QAezMlwz
ImjV4yJNmhQQKVAQbPVRQAWl4M/wgsD2DjQLbO2eF4E+TMhhrb2vcRKPWBbijjM=
=Yl+F
-----END PGP SIGNATURE-----

Changing the name of a resource

John Anthony — 2012-05-23T21:50:44

All:

Wanted to change the name of the drbd resource to better reflect its
functional use.

In test, Tried changing the file and resource name on the secondary side,
adjusting and re-connecting. And other slightly different steps, to see
what can work.

The results are that when re-connecting after changing the file name - the
primary side seems to think that the device is out of sync and becomes the
sync source but the secondary side will have none of it and goes it
'WFConnection' state.

Find below the log extract when the secondary side is connected after the
resource is renamed. ( From the log it seems that it does become the sync
target and actually syncs, but does not like something).

Is there a known sequence of steps that can work in this case ? Need I
experiment any further ? What else can I try ?

-JA

block drbd0: conn( StandAlone -> Unconnected )
block drbd0: Starting receiver thread (from drbd0_worker [32028])
block drbd0: receiver (re)started
block drbd0: conn( Unconnected -> WFConnection )
block drbd0: Handshake successful: Agreed network protocol version 96
block drbd0: Peer authenticated using 16 bytes of 'md5' HMAC
block drbd0: conn( WFConnection -> WFReportParams )
block drbd0: Starting asender thread (from drbd0_receiver [14379])
block drbd0: data-integrity-alg: md5
block drbd0: drbd_sync_handshake:
block drbd0: self
A3DA23FAA568B544:0000000000000000:CC820BAF75D3008A:CC810BAF75D3008B bits:0
flags:0
block drbd0: peer
518B27BC03329A91:A3DB23FAA568B545:A3DA23FAA568B545:CC820BAF75D3008B
bits:721870 flags:0
block drbd0: Did not got last syncUUID packet, corrected:
block drbd0: peer
518B27BC03329A91:A3DA23FAA568B545:CC820BAF75D3008B:CC820BAF75D3008B
bits:721870 flags:0
block drbd0: uuid_compare()=-1 by rule 51
block drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT )
disk( UpToDate -> Outdated ) pdsk( DUnknown -> UpToDate )
block drbd0: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 239(1),
total 239; compression: 99.9%
block drbd0: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 239(1),
total 239; compression: 99.9%
block drbd0: conn( WFBitMapT -> WFSyncUUID )
block drbd0: updated sync uuid
A3DB23FAA568B544:0000000000000000:CC820BAF75D3008A:CC810BAF75D3008B
block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0
block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0
exit code 0 (0x0)
block drbd0: conn( WFSyncUUID -> SyncTarget ) disk( Outdated ->
Inconsistent )
block drbd0: Began resync as SyncTarget (will sync 2887480 KB [721870 bits
set]).
block drbd0: Resync done (total 9 sec; paused 0 sec; 320828 K/sec)
block drbd0: 100 % had equal check sums, eliminated: 2887480K; transferred
0K total 2887480K
block drbd0: updated UUIDs
518B27BC03329A90:0000000000000000:A3DB23FAA568B544:A3DA23FAA568B545
block drbd0: conn( SyncTarget -> Connected ) disk( Inconsistent -> UpToDate
)
block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0
block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0 exit
code 0 (0x0)
block drbd0: bitmap WRITE of 0 pages took 0 jiffies
block drbd0: 0 KB (0 bits) marked out-of-sync by on disk bit-map.
block drbd0: peer( Primary -> Unknown ) conn( Connected -> TearDown ) pdsk(
UpToDate -> DUnknown )
block drbd0: asender terminated
block drbd0: Terminating asender thread
block drbd0: Connection closed
block drbd0: conn( TearDown -> Unconnected )
block drbd0: receiver terminated
block drbd0: Restarting receiver thread
block drbd0: receiver (re)started
block drbd0: conn( Unconnected -> WFConnection )
block drbd0: conn( WFConnection -> Disconnecting )
block drbd0: Discarding network configuration.
block drbd0: Connection closed
block drbd0: conn( Disconnecting -> StandAlone )
block drbd0: receiver terminated
block drbd0: Terminating receiver thread
block drbd0: conn( StandAlone -> Unconnected )
block drbd0: Starting receiver thread (from drbd0_worker [32028])
block drbd0: receiver (re)started
block drbd0: conn( Unconnected -> WFConnection )
_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

Recovering from erroneous sync state

Zev Weiss — 2012-05-23T20:14:19

Hi,

I'm running DRBD 8.3.12, and recently hit what looks to me like a bug that was listed as fixed in 8.3.13 -- getting into a state where both nodes are in SyncSource (it's just stuck like that, going nowhere).  Luckily this happened on a test resource and not a live one, so it's not a big problem, but I was wondering if there were any known ways of recovering it without doing anything disruptive to the other resources (e.g. rebooting or unloading the kernel module).

I've tried 'drbdadm down', but it just hangs -- anyone have any other suggestions?  It doesn't really matter to me if it wipes the resource or anything, I'd just like to have my test device back in a working state without disturbing anything else.

Thanks,
Zev Weiss

need discribtion and help

Mahmoud Alshinhab — 2012-05-23T15:12:04

Dears Kindly help as I Can’t create the drbd device because of this
error message


drbdmeta /dev/drbd0 v08 /dev/sda2 internal create-md' terminated with
exit code 40


global {
                usage-count yes;
}
Common {
                Syncer {
                rate 10M;
}
}
resource r0 {
                protocol C;
                on master {
                                device   /dev/drbd1;
                                disk        /dev/sdb1;
                                address 192.168.1.1;7789;
                                meta-disk internal;
}
                on slave{
                                device   /dev/drbd1;
                                disk        /dev/sdb1;
                                address 192.168.1.2;7789;
                                meta-disk internal;
}

}

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          38      305203+  83  Linux
/dev/sda2              39        2349    18563107+  83  Linux
/dev/sda3            2350        2610     2096482+  82  Linux swap / Solaris

Disk /dev/sdb: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         652     5237158+  83  Linux


[root< at >master ~]# drbdadm create-md r0
v08 Magic number not found
md_offset 5362843648
al_offset 5362810880
bm_offset 5362647040

Found ext3 filesystem which uses 5237156 kB
current configuration leaves usable 5236960 kB

Device size would be truncated, which
would corrupt data and result in
'access beyond end of device' errors.
You need to either
   * use external meta data (recommended)
   * shrink that filesystem first
   * zero out the device (destroy the filesystem)
Operation refused.

Command 'drbdmeta /dev/drbd1 v08 /dev/sdb1 internal create-md'
terminated with exit code 40
drbdadm aborting

Moving a DRBD cluster from physical machines to VMWaremachines

Keith Christian — 2012-05-23T15:29:20

Looking for guidance from Linbit, or the list, about DRBD's disks
remaining on two separate physical servers, except that the peer
servers are virtualized?

For instance: Writes of approximately 18,000 blocks per second for the
busy hours, as reported by SAR.  How much a performance hit is there
with the same hardware after VMWare is in the picture?  (I'm sure
there are VMWare config settings to optimize disk reads/writes for an
application like DRBD.)


Thanks.


=====Keith

Reasons not to use allow-two-primaries with DRDB

2012-05-18T16:29:11

Hello,

I am in the process of setting up DRBD on my servers, the network
bandwidth being the bottleneck.  After having evaluated GlusterFS I
realised, that I need the instant read access offered by DRBD.

Logically I am able to separate partitions that would require access
from both nodes, and partitions where an asynchronous master-slave
sync is sufficient.  But as far as I understand, the benefits from
using Protocol A instead of C are limited, when the network is stable.

My question:
Are there any additional benefits from NOT using two primaries or
additional risks when using it? eg. would there be significant
performance gain by using ext4 instead of GFS2/OCFS2? Anything else I
should take into consideration?

Thanks for any ideas or pointers where to look.

Karel

DRBD block script with Xen XL toolstack

Chris Dickson — 2012-05-19T12:42:58

Hello,

Currently it seems that the drbd disk type with Xen's XL toolstack (vs
Xend) to get the automatic promotion/demotion behavior of drbd devices is
not supported by default; is there a way to get Xend's current block-drbd
script behavior with XL?

Thanks,

Chris
_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

drbd wrong lower device doubt

陈楠 — 2012-05-18T07:19:42


Hi All, I have some doubts about drbd. I have configure two servers as Host A and Host B. Host A drbd configuration is like this: 
resource r0 {
        on A {
                device /dev/drbd0;
                disk /dev/vg01/share;
                address 2.2.2.150:7788;
                meta-disk internal;
        }
        on B {
                device /dev/drbd0;
                disk /dev/vg01/share;
                address 2.2.2.151:7788;
                meta-disk internal;
        }
}
and Host B is like this:
resource r0 {
        on A {
                device /dev/drbd0;
                disk /dev/vg02/share;
                address 2.2.2.150:7788;
                meta-disk internal;
        }
        on B {
                device /dev/drbd0;
                disk /dev/vg02/share;
                address 2.2.2.151:7788;
                meta-disk internal;
        }
}
You can notice that Host A and Host B configuration file is not same. Actually Host A lower device is /dev/vg01/share and Host B lower device is  /dev/vg02/share. The specified destination lower device is wrong in each server. Network setting is right . I set Host A disk state to UpToDate and Host B disk state inconsistent. I find that Host A is syncing to Host B.  Why it can work regularly when I configure wrong lower device.

_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

I need Reset DRBD Service

Cristian Caceres — 2012-05-17T21:14:42

Hi all, I have little experience in drbd, in fact I received as a legacy a
system with this implementation, my problem is that one of the nodes, the
secondary, we had to restart, but now I see they are not connected
according to, I have sought some solution without success, please if
someone can help me decipher this I would appreciate.


the status of each server is the following:

Primary Server:

drbd driver loaded OK; device status:
version: 8.2.6 (api:88/proto:86-88)
GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by
root-wDAxgLocYoT0MrXhQeckh6qrw+pMJB36232DYX7GltoAvxtiuMwx3w< at >public.gmane.org, 2008-12-23 13:00:05
m:res cs st ds p mounted fstype
0:??not-found?? StandAlone Primary/Unknown UpToDate/DUnknown -

Secondary Server:

drbd driver loaded OK; device status:
version: 8.2.6 (api:88/proto:86-88)
GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by
root-wDAxgLocYoT0MrXhQeckh6qrw+pMJB36232DYX7GltoAvxtiuMwx3w< at >public.gmane.org, 2008-12-23 13:00:05
m:res cs st ds p mounted fstype
0:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown B

Thanks..

rca
_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

"PingAck not received" messages

Matthew Bloch — 2012-05-16T20:11:05

I'm trying to understand a symptom for a client who uses drbd to run
sets of virtual machines between three pairs of servers (v1a/v1b,
v2a/v2b, v3a/v3b), and I wanted to understand a bit better how DRBD I/O
is buffered depending on what mode is chosen, and buffer settings.

Firstly, it surprised me that even in replication mode "A", the system
still seemed limited by by the bandwidth between nodes.  I found this
out when the customer's bonded interface had flipped over to its 100Mb
backup connection, and suddenly they had I/O problems.  While I was
investigating this and running tests, I noticed that switching to mode A
didn't help, even when measuring short transfers that I'd expect would
fit into reasonable-sized buffers.  What kind of buffer size can I
expect from an "auto-tuned" DRBD?  It seems important to be able to
cover bursts without leaning on the network, so I'd like to know whether
that's possible with some special tuning.

The other problem is the "PingAck not received" messages that have been
littering the logs of the v3a/v3b servers for the last couple of weeks,
e.g. this has been happening every few hours for one DRBD or another:

May 14 08:21:45 v3b kernel: [661127.869500] block drbd10: PingAck did
not arrive in time.
May 14 08:21:45 v3b kernel: [661127.875553] block drbd10: peer( Primary
-> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate ->
DUnknown )
May 14 08:21:45 v3b kernel: [661127.875562] block drbd10: asender terminated
May 14 08:21:45 v3b kernel: [661127.875564] block drbd10: Terminating
drbd10_asender
May 14 08:21:45 v3b kernel: [661127.875597] block drbd10: short read
expecting header on sock: r=-512
May 14 08:21:45 v3b kernel: [661127.882896] block drbd10: Connection closed
May 14 08:21:45 v3b kernel: [661127.882899] block drbd10: conn(
NetworkFailure -> Unconnected )
May 14 08:21:45 v3b kernel: [661127.882904] block drbd10: receiver
terminated
May 14 08:21:45 v3b kernel: [661127.882908] block drbd10: Restarting
drbd10_receiver
May 14 08:21:45 v3b kernel: [661127.882910] block drbd10: receiver
(re)started
May 14 08:21:45 v3b kernel: [661127.882913] block drbd10: conn(
Unconnected -> WFConnection )
May 14 08:21:46 v3b kernel: [661129.123506] block drbd10: Handshake
successful: Agreed network protocol version 91
May 14 08:21:46 v3b kernel: [661129.123511] block drbd10: conn(
WFConnection -> WFReportParams )
May 14 08:21:46 v3b kernel: [661129.123535] block drbd10: Starting
asender thread (from drbd10_receiver [31418])
May 14 08:21:46 v3b kernel: [661129.123876] block drbd10:
data-integrity-alg: <not-used>
May 14 08:21:46 v3b kernel: [661129.123898] block drbd10:
drbd_sync_handshake:
May 14 08:21:46 v3b kernel: [661129.123900] block drbd10: self
C5DC68A8AFD5BFEC:0000000000000000:7EB45F3A26B3BD72:2EC9659EFC4BC513
bits:0 flags:0
May 14 08:21:46 v3b kernel: [661129.123903] block drbd10: peer
F8BB238D22A7ACFF:C5DC68A8AFD5BFED:7EB45F3A26B3BD72:2EC9659EFC4BC513
bits:0 flags:0
May 14 08:21:46 v3b kernel: [661129.123905] block drbd10:
uuid_compare()=-1 by rule 50
May 14 08:21:46 v3b kernel: [661129.123908] block drbd10: peer( Unknown
-> Primary ) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown ->
UpToDate )
May 14 08:21:46 v3b kernel: [661129.138101] block drbd10: conn(
WFBitMapT -> WFSyncUUID )
May 14 08:21:46 v3b kernel: [661129.139563] block drbd10: helper
command: /sbin/drbdadm before-resync-target minor-10
May 14 08:21:46 v3b kernel: [661129.140282] block drbd10: helper
command: /sbin/drbdadm before-resync-target minor-10 exit code 0 (0x0)
May 14 08:21:46 v3b kernel: [661129.140286] block drbd10: conn(
WFSyncUUID -> SyncTarget ) disk( UpToDate -> Inconsistent )
May 14 08:21:46 v3b kernel: [661129.140292] block drbd10: Began resync
as SyncTarget (will sync 0 KB [0 bits set]).
May 14 08:21:47 v3b kernel: [661129.693954] block drbd10: Resync done
(total 1 sec; paused 0 sec; 0 K/sec)
May 14 08:21:47 v3b kernel: [661129.693961] block drbd10: conn(
SyncTarget -> Connected ) disk( Inconsistent -> UpToDate )
May 14 08:21:47 v3b kernel: [661129.693969] block drbd10: helper
command: /sbin/drbdadm after-resync-target minor-10
May 14 08:21:47 v3b kernel: [661129.694725] block drbd10: helper
command: /sbin/drbdadm after-resync-target minor-10 exit code 0 (0x0)

I've not been able to correlate these ping drops and reconnections to
any of:

1) interface capacity issues (a few times we might make a 400Mb spike,
but sometimes there's none at all);

2) loss of connectivity or ARP problems on the two servers' dedicated
DRBD interfaces (i.e. I've got an unbroken log of pings between the two
servers);

3) any kernel grumbles about the network interface, bonding, RAID or
anything remotely hardware-related.  Apart from the drbd messages
there's no other chatter from the kernel.

The customer's other two pairs of servers have been running 18 months
and not exhibited this behaviour.

The customer hasn't given me the data to show these blips (which are
anything from 2s-30s) correspond to any real performance problems and I
don't have access to the inside of their VMs to check for myself.  So my
questions are - would you expect these disconnections to cause
variations in I/O bandwidth or responsiveness?

And secondly, what should I be doing about it?  My unsatisfactory
response to the customer's worry is to reconnect all the drbds with a
longer ping-timeout, and in 10 hours it hasn't reoccurred, which is an
unusually long record.  I will be more convinced by the end of the day.

Even if that does solve these messages, I'm curious as to the cause.
We've not hit a network bandwidth ceiling, and so we've definitely not
hit an I/O ceiling (which is 4x146GB 15kRPM discs, RAID10, HP RAID).  I
can accept that some VMs will use more bandwidth than others, and so it
wouldn't be surprising that one VM on the machine was the "cause".

But when the disconnections happen, they appear to be completely random.
 Checking with grep/uniq -c, I see out of the 11 devices on the systems,
it happens pretty randomly (and drbd10 is just a test, getting
absolutely zero I/O).

      5 drbd0:
      5 drbd1:
     11 drbd2:
      8 drbd3:
     11 drbd4:
      4 drbd5:
      6 drbd6:
      7 drbd7:
      5 drbd8:
     14 drbd9:
     12 drbd10:
      7 drbd11:

So even if upping the ping time stops the problem, and even if the
effects of the disconnect/reconnect cycles are harmless - why might DRBD
exhibit these symptoms on one pair of servers, but not two other sets?
Is there some I/O pattern that might cause pings to get lost, even over
a lightly-loaded gigabit link?

Thanks for any insights in advance.

NFS not starting with heartbeat

Marcel Kraan — 2012-05-16T19:40:09

Hello,

I use 2 servers with CentOS 6.2 

But on 1 server (kvmstorage1) ifs is not starting after a restart or when i shutdown heartbeat and restart is later.

# this is my resources file? it start not all services i have given in the haresources file?
Do i something wrong?


#kvmstorage1
cat /etc/ha.d/haresources
kvmstorage1.localdomain IPaddr::192.168.123.209/24/eth0 drbddisk::main Filesystem::/dev/drbd0::/datastore::ext4 nfs nfslock rpcidmapd mysql

ResourceManager[2506]:2012/05/16_21:34:40 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /datastore ext4 start
Filesystem[2933]:2012/05/16_21:34:40 INFO: Running start for /dev/drbd0 on /datastore
Filesystem[2921]:2012/05/16_21:34:41 INFO:  Success
ResourceManager[2506]:2012/05/16_21:34:41 info: Running /etc/init.d/nfslock  start
ResourceManager[2506]:2012/05/16_21:34:41 info: Running /etc/init.d/rpcidmapd  start
ResourceManager[2506]:2012/05/16_21:34:42 info: Running /etc/init.d/mysqld  start
May 16 21:34:43 kvmstorage1.localdomain heartbeat: [2489]: info: local HA resource acquisition completed (standby).
May 16 21:34:43 kvmstorage1.localdomain heartbeat: [1583]: info: Standby resource acquisition done [foreign].
May 16 21:34:43 kvmstorage1.localdomain heartbeat: [1583]: info: Initial resource acquisition complete (auto_failback)
May 16 21:34:43 kvmstorage1.localdomain heartbeat: [1583]: info: remote resource transition completed.


#kvmstorage2
cat /etc/ha.d/haresources
kvmstorage1.localdomain IPaddr::192.168.123.209/24/eth0 drbddisk::main Filesystem::/dev/drbd0::/datastore::ext4 nfs nfslock rpcidmapd mysql

Filesystem[16037]:2012/05/16_21:33:53 INFO:  Resource is stopped
ResourceManager[15787]:2012/05/16_21:33:53 info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /datastore ext4 start
Filesystem[16117]:2012/05/16_21:33:53 INFO: Running start for /dev/drbd0 on /datastore
Filesystem[16109]:2012/05/16_21:33:53 INFO:  Success
ResourceManager[15787]:2012/05/16_21:33:54 info: Running /etc/init.d/nfs  start
ResourceManager[15787]:2012/05/16_21:33:54 info: Running /etc/init.d/nfslock  start
ResourceManager[15787]:2012/05/16_21:33:54 info: Running /etc/init.d/mysqld  start
mach_down[15761]:2012/05/16_21:33:56 info: /usr/share/heartbeat/mach_down: nice_failback: foreign resources acquired
May 16 21:33:56 kvmstorage2.localdomain heartbeat: [1528]: info: mach_down takeover complete.
mach_down[15761]:2012/05/16_21:33:56 info: mach_down takeover complete for node kvmstorage1.localdomain.

Drbd many blocks out of sync

Vladimir Kuklin — 2012-05-16T07:58:36

Hi guys

I am experiencing very strange behaviour of DRBD.

My setup is:


Two absolutely identical Supermicro nodes using LSI 9265-8i controller 
with SAS disks.

Scientific Linux 6.2 with latest OpenVZ stable kernel that uses drbd 8.3.10.

the excerpt from my drbd.conf is following:

...
resource r1 {
     net
         {
         max-buffers 8000;
         max-epoch-size 8000;
         sndbuf-size 2M;
         allow-two-primaries;
         after-sb-0pri discard-zero-changes;
         after-sb-1pri discard-secondary;
         after-sb-2pri disconnect;
#        data-integrity-alg crc32c;
         ping-int 25;
     }
     startup {
         become-primary-on both;
     }



     syncer {
         rate 100M;
         al-extents 3383;
         csums-alg crc32c;
         verify-alg crc32c;
         }

     disk {
         fencing resource-only;
#        no-disk-barrier;
#        no-disk-flushes;
         }
         handlers
         {
         split-brain "/usr/lib/drbd/notify-split-brain.sh root";
         out-of-sync "/usr/lib/drbd/notify-out-of-sync.sh root";
#       fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
#       after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
         }
     protocol C;

     on srv10 {
         device     /dev/drbd1;
         disk       /dev/sdf1;
         address    192.168.27.11:7789;
         meta-disk internal;
         }

       on srv11 {
         device    /dev/drbd1;
         disk      /dev/sdf1;
         address   192.168.27.12:7789;
         meta-disk internal;
         }
}
...

The problem is that after initial synchronization if I run "drbdadm 
verify r1", I get a bunch of out-of-sync blocks. Then I do disconnect 
and connect of this resource and run "drbdadm verify r1" again and then 
I again do get a bunch of out-of-sync blocks. Some of them are 
false-positives and some of them are really out of sync as dd shows 
(both with iflags=direct and without). And what is important: there is 
no write operations on this device. Nothing is written to it, but I get 
a bunch of out-of-sync blocks any time I run verify and resync DRBD.

[root< at >srv10 vvk]# drbdadm verify r1
[root< at >srv10 vvk]# cat /proc/drbd
version: 8.3.10 (api:88/proto:86-96)
GIT-hash: 5c0b0469666682443d4785d90a2c603378f9017b build by 
phil< at >fat-tyre, 2011-01-28 12:17:35

  1: cs:VerifyS ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
     ns:1568452 nr:0 dw:4 dr:39777412 al:1 bm:1300 lo:333 pe:0 ua:367 
ap:0 ep:1 wo:b oos:484868
         [>....................] verified:  2.3% (9328/9536)M
         finish: 0:01:29 speed: 106,784 (106,784) want: 102,400 K/sec
[root< at >srv10 vvk]# cat /proc/drbd
version: 8.3.10 (api:88/proto:86-96)
GIT-hash: 5c0b0469666682443d4785d90a2c603378f9017b build by 
phil< at >fat-tyre, 2011-01-28 12:17:35

  1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
     ns:1568452 nr:0 dw:4 dr:49330856 al:1 bm:1300 lo:0 pe:0 ua:0 ap:0 
ep:1 wo:b oos:724448
[root< at >srv10 vvk]# dmesg | tail -10

[ 2267.737437] block drbd1: helper command: /sbin/drbdadm 
before-resync-source minor-1 exit code 0 (0x0)
[ 2267.737445] block drbd1: conn( WFBitMapS -> SyncSource ) pdsk( 
Consistent -> Inconsistent )
[ 2267.737455] block drbd1: Began resync as SyncSource (will sync 724448 
KB [181112 bits set]).
[ 2267.737494] block drbd1: updated sync UUID 
5B5B2B2EE43F8757:7BE37645CD25FF6D:7BE27645CD25FF6D:0001000000000000
[ 2276.569106] block drbd1: Resync done (total 8 sec; paused 0 sec; 
90556 K/sec)
[ 2276.569113] block drbd1: 51 % had equal check sums, eliminated: 
371216K; transferred 353232K total 724448K
[ 2276.569120] block drbd1: updated UUIDs 
5B5B2B2EE43F8757:0000000000000000:7BE37645CD25FF6D:7BE27645CD25FF6D
[ 2276.569129] block drbd1: conn( SyncSource -> Connected ) pdsk( 
Inconsistent -> UpToDate )
[ 2276.569727] block drbd1: bitmap WRITE of 52 pages took 0 jiffies
[ 2276.569750] block drbd1: 0 KB (0 bits) marked out-of-sync by on disk 
bit-map.

[root< at >srv10 vvk]# cat /proc/drbd
version: 8.3.10 (api:88/proto:86-96)
GIT-hash: 5c0b0469666682443d4785d90a2c603378f9017b build by 
phil< at >fat-tyre, 2011-01-28 12:17:35

  1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
     ns:353232 nr:0 dw:4 dr:50055636 al:1 bm:1410 lo:0 pe:0 ua:0 ap:0 
ep:1 wo:b oos:0
[root< at >srv10 vvk]# drbdadm verify r1

[root< at >srv10 vvk]# cat /proc/drbd
version: 8.3.10 (api:88/proto:86-96)
GIT-hash: 5c0b0469666682443d4785d90a2c603378f9017b build by 
phil< at >fat-tyre, 2011-01-28 12:17:35

  1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
     ns:353232 nr:0 dw:4 dr:59822788 al:1 bm:1410 lo:0 pe:0 ua:0 ap:0 
ep:1 wo:b oos:470532


Is this normal DRBD behaviour?

Partitioning a drbd device

Chris Dickson — 2012-05-14T21:41:31

Hello,

I'm trying to partition a drbd device that is backed by an LVM partition.
So I guess you could call it a partition within a partition. The partitions
seem to be getting created fine (I used cfdisk on /dev/drbd1), but I can't
seem to figure out how to actually get the partitions to show up in /dev
and be mountable. cfdisk sees them as drbd1p1 and drbd1p2, but when I run a
partprobe I get:

Error: Error informing the kernel about modifications to partition
/dev/drbd1p1 -- Invalid argument.  This means Linux won't know about any
changes you made to /dev/drbd1p1 until you reboot -- so you shouldn't mount
it or use it in any way before rebooting.
Error: Failed to add partition 1 (Invalid argument)

Unfortunately I'm not in a position to reboot the machine right now, and
even if that was a solution I would need this to happen on the fly while
the machine is running. Any thoughts?

Thanks,

Chris
_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

Machine recycle causes drbd init to hang

John Anthony — 2012-05-14T18:09:55

All:

In our use case - we would like the devices to come up in "disconnected"
state - the state at which the machine was recycled and the peer is
disconnected to.

Init bring up devices in cs:WFConnection state and since the peer will not
connect, subsequent parts of the init sequence does not run.

Will look into the script, but wondering if there are any quick hits for
this.

-JA
_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

DRBD PACEMAKER

Antonio Ramos — 2012-05-13T17:18:15

I configured a cluster with drbd pacemaker and seems to work fine, however I
get an error in one of resources:

Failed actions:
     drbdmeta: 1_demote_0 (node = opf2.vera.es, call = 135, rc = -2, status
= Timed Out):

What is 1_demote_0?
Thanks in advance
_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

servers out of sync

Marcel Kraan — 2012-05-13T13:25:11

i don't get it synced again.
they are now both stand alone?
i can ping them both.

don't  have any options left.

[root< at >kvmstorage1 drbd.d]# cat /proc/drbd 
version: 8.3.12 (api:88/proto:86-96)
GIT-hash: e2a8ef4656be026bbae540305fcb998a5991090f build by phil< at >Build64R6, 2012-04-08 09:36:52
 0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r-----
    ns:0 nr:0 dw:412 dr:9926 al:2 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:280

[root< at >kvmstorage2 drbd.d]# cat /proc/drbd 
version: 8.3.12 (api:88/proto:86-96)
GIT-hash: e2a8ef4656be026bbae540305fcb998a5991090f build by phil< at >Build64R6, 2012-04-08 09:36:52
 0: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown   r-----
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:264




/var/log/messages on 2 servers

[root< at >kvmstorage2 drbd.d]# service drbd restart
Stopping all DRBD resources: May 13 15:14:13 kvmstorage2 kernel: block drbd0: disk( UpToDate -> Failed ) 
May 13 15:14:13 kvmstorage2 kernel: block drbd0: disk( Failed -> Diskless ) 
May 13 15:14:13 kvmstorage2 kernel: block drbd0: drbd_bm_resize called with capacity == 0
May 13 15:14:13 kvmstorage2 kernel: block drbd0: worker terminated
May 13 15:14:13 kvmstorage2 kernel: block drbd0: Terminating worker thread
May 13 15:14:13 kvmstorage2 kernel: drbd: module cleanup done.
.
Starting DRBD resources: May 13 15:14:13 kvmstorage2 kernel: drbd: initialized. Version: 8.3.12 (api:88/proto:86-96)
May 13 15:14:13 kvmstorage2 kernel: drbd: GIT-hash: e2a8ef4656be026bbae540305fcb998a5991090f build by phil< at >Build64R6, 2012-04-08 09:36:52
May 13 15:14:13 kvmstorage2 kernel: drbd: registered as block device major 147
May 13 15:14:13 kvmstorage2 kernel: drbd: minor_table < at > 0xffff88020f7257c0
[ d(main) May 13 15:14:13 kvmstorage2 kernel: block drbd0: Starting worker thread (from cqueue [1344])
May 13 15:14:13 kvmstorage2 kernel: block drbd0: disk( Diskless -> Attaching ) 
May 13 15:14:13 kvmstorage2 kernel: block drbd0: Found 6 transactions (34 active extents) in activity log.
May 13 15:14:13 kvmstorage2 kernel: block drbd0: Method to ensure write ordering: barrier
May 13 15:14:13 kvmstorage2 kernel: block drbd0: max BIO size = 131072
May 13 15:14:13 kvmstorage2 kernel: block drbd0: drbd_bm_resize called with capacity == 6920386232
May 13 15:14:13 kvmstorage2 kernel: block drbd0: resync bitmap: bits=865048279 words=13516380 pages=26400
May 13 15:14:13 kvmstorage2 kernel: block drbd0: size = 3300 GB (3460193116 KB)
May 13 15:14:13 kvmstorage2 kernel: block drbd0: bitmap READ of 26400 pages took 198 jiffies
May 13 15:14:13 kvmstorage2 kernel: block drbd0: recounting of set bits took additional 90 jiffies
May 13 15:14:13 kvmstorage2 kernel: block drbd0: 264 KB (66 bits) marked out-of-sync by on disk bit-map.
May 13 15:14:13 kvmstorage2 kernel: block drbd0: disk( Attaching -> UpToDate ) 
May 13 15:14:13 kvmstorage2 kernel: block drbd0: attached to UUIDs C12A485E56F51104:9555562D91EACAC2:A615ADBD6A39BD99:A614ADBD6A39BD99
n(main) May 13 15:14:13 kvmstorage2 kernel: block drbd0: conn( StandAlone -> Unconnected ) 
May 13 15:14:13 kvmstorage2 kernel: block drbd0: Starting receiver thread (from drbd0_worker [6484])
May 13 15:14:13 kvmstorage2 kernel: block drbd0: receiver (re)started
May 13 15:14:13 kvmstorage2 kernel: block drbd0: conn( Unconnected -> WFConnection ) 
]May 13 15:14:14 kvmstorage2 kernel: block drbd0: Handshake successful: Agreed network protocol version 96
May 13 15:14:14 kvmstorage2 kernel: block drbd0: conn( WFConnection -> WFReportParams ) 
May 13 15:14:14 kvmstorage2 kernel: block drbd0: Starting asender thread (from drbd0_receiver [6494])
May 13 15:14:14 kvmstorage2 kernel: block drbd0: data-integrity-alg: <not-used>
May 13 15:14:14 kvmstorage2 kernel: block drbd0: drbd_sync_handshake:
May 13 15:14:14 kvmstorage2 kernel: block drbd0: self C12A485E56F51104:9555562D91EACAC2:A615ADBD6A39BD99:A614ADBD6A39BD99 bits:66 flags:0
May 13 15:14:14 kvmstorage2 kernel: block drbd0: peer E33CEADD1FF28EE1:9555562D91EACAC3:A615ADBD6A39BD98:A614ADBD6A39BD99 bits:70 flags:0
May 13 15:14:14 kvmstorage2 kernel: block drbd0: uuid_compare()=100 by rule 90
May 13 15:14:14 kvmstorage2 kernel: block drbd0: helper command: /sbin/drbdadm initial-split-brain minor-0
May 13 15:14:14 kvmstorage2 kernel: block drbd0: helper command: /sbin/drbdadm initial-split-brain minor-0 exit code 0 (0x0)
May 13 15:14:14 kvmstorage2 kernel: block drbd0: Split-Brain detected but unresolved, dropping connection!
May 13 15:14:14 kvmstorage2 kernel: block drbd0: helper command: /sbin/drbdadm split-brain minor-0
May 13 15:14:14 kvmstorage2 kernel: block drbd0: meta connection shut down by peer.
May 13 15:14:14 kvmstorage2 kernel: block drbd0: helper command: /sbin/drbdadm split-brain minor-0 exit code 0 (0x0)
May 13 15:14:14 kvmstorage2 kernel: block drbd0: conn( WFReportParams -> Disconnecting ) 
May 13 15:14:14 kvmstorage2 kernel: block drbd0: error receiving ReportState, l: 4!
May 13 15:14:14 kvmstorage2 kernel: block drbd0: asender terminated
May 13 15:14:14 kvmstorage2 kernel: block drbd0: Terminating asender thread
May 13 15:14:14 kvmstorage2 kernel: block drbd0: Connection closed
May 13 15:14:14 kvmstorage2 kernel: block drbd0: conn( Disconnecting -> StandAlone ) 
May 13 15:14:14 kvmstorage2 kernel: block drbd0: receiver terminated
May 13 15:14:14 kvmstorage2 kernel: block drbd0: Terminating receiver thread



second server (primary right now)

root< at >kvmstorage1 drbd.d]# service drbd restart
Stopping all DRBD resources: umount: /datastore: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
/dev/drbd0: State change failed: (-12) Device is held open by someone
May 13 15:16:22 kvmstorage1 kernel: block drbd0: State change failed: Device is held open by someone
May 13 15:16:22 kvmstorage1 kernel: block drbd0:   state = { cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----- }
May 13 15:16:22 kvmstorage1 kernel: block drbd0:  wanted = { cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----- }
ERROR: Module drbd is in use
.
Starting DRBD resources: [ n(main) May 13 15:16:22 kvmstorage1 kernel: block drbd0: conn( StandAlone -> Unconnected ) 
May 13 15:16:22 kvmstorage1 kernel: block drbd0: Starting receiver thread (from drbd0_worker [1441])
May 13 15:16:22 kvmstorage1 kernel: block drbd0: receiver (re)started
May 13 15:16:22 kvmstorage1 kernel: block drbd0: conn( Unconnected -> WFConnection ) 
]..........
***************************************************************
 DRBD's startup script waits for the peer node(s) to appear.
 - In case this node was already a degraded cluster before the
   reboot the timeout is 0 seconds. [degr-wfc-timeout]
 - If the peer was available before the reboot the timeout will
   expire after 0 seconds. [wfc-timeout]
   (These values are for resource 'drbd'; 0 sec -> wait forever)  
(i had to restart drbd on the second node)
 To abort waiting enter 'yes' [  54]:May 13 15:17:16 kvmstorage1 kernel: block drbd0: Handshake successful: Agreed network protocol version 96
May 13 15:17:16 kvmstorage1 kernel: block drbd0: conn( WFConnection -> WFReportParams ) 
May 13 15:17:16 kvmstorage1 kernel: block drbd0: Starting asender thread (from drbd0_receiver [7458])
May 13 15:17:16 kvmstorage1 kernel: block drbd0: data-integrity-alg: <not-used>
May 13 15:17:16 kvmstorage1 kernel: block drbd0: drbd_sync_handshake:
May 13 15:17:16 kvmstorage1 kernel: block drbd0: self E33CEADD1FF28EE1:9555562D91EACAC3:A615ADBD6A39BD98:A614ADBD6A39BD99 bits:70 flags:0
May 13 15:17:16 kvmstorage1 kernel: block drbd0: peer C12A485E56F51104:9555562D91EACAC2:A615ADBD6A39BD99:A614ADBD6A39BD99 bits:66 flags:0
May 13 15:17:16 kvmstorage1 kernel: block drbd0: uuid_compare()=100 by rule 90
May 13 15:17:16 kvmstorage1 kernel: block drbd0: helper command: /sbin/drbdadm initial-split-brain minor-0
May 13 15:17:16 kvmstorage1 kernel: block drbd0: helper command: /sbin/drbdadm initial-split-brain minor-0 exit code 0 (0x0)
May 13 15:17:16 kvmstorage1 kernel: block drbd0: Split-Brain detected but unresolved, dropping connection!
May 13 15:17:16 kvmstorage1 kernel: block drbd0: helper command: /sbin/drbdadm split-brain minor-0

May 13 15:17:16 kvmstorage1 kernel: block drbd0: helper command: /sbin/drbdadm split-brain minor-0 exit code 0 (0x0)
May 13 15:17:16 kvmstorage1 kernel: block drbd0: conn( WFReportParams -> Disconnecting ) 
May 13 15:17:16 kvmstorage1 kernel: block drbd0: error receiving ReportState, l: 4!
May 13 15:17:16 kvmstorage1 kernel: block drbd0: asender terminated
May 13 15:17:16 kvmstorage1 kernel: block drbd0: Terminating asender thread
May 13 15:17:16 kvmstorage1 kernel: block drbd0: Connection closed
May 13 15:17:16 kvmstorage1 kernel: block drbd0: conn( Disconnecting -> StandAlone ) 
May 13 15:17:16 kvmstorage1 kernel: block drbd0: receiver terminated
May 13 15:17:16 kvmstorage1 kernel: block drbd0: Terminating receiver thread


_______________________________________________
drbd-user mailing list
drbd-user-cunTk1MwBs8qoQakbn7OcQ< at >public.gmane.org
http://lists.linbit.com/mailman/listinfo/drbd-user

drbd and heartbeat

Marcel Kraan — 2012-05-11T12:21:58

I have a 3TB disk shared for drbd0

the syncing is with 30MB/sec and it takes 2 days to complete

While syncing heartbeat is not working (is this correct?)

when i put both servers offline the disks need to resync again.. (2 days)

Is this normal?  

Is there a new way for clustering?