gmane.comp.linux.drbd

startup hang after "yes"

Dan Barker — 2012-05-26T17:23:00

I'm building a new drbd machine. I put 8.4.0 on a Debian 603 and all looks
fine except ...

Since I'm testing, I don't have another node. I did create-md and then
primary --force. At boot time, there is no peer, so I get the count-up to
yes. When I enter yes, nothing happens.

If I ssh in and stop/start drbd, all is normal and my initialization scripts
finally run (the ones after drbd).

What can I do to stop the hang?

Other possibly mitigating factors:
 There is no Ethernet cable connected to the NIC for DRBD synchronization.
 There is only one drbd resource defined, drbd3 (no 0, 1 or 2).

I chose 8.4.0 to match the peer in the environment. I thought about 8.4.1 or
8.3.13, but I'll just update everybody to 9 soon.

Dan

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

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

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/wgsD2DjQLbO2

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 )
bl

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

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

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-f

"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
l

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:

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-

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.g

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