Hello,
my problem seems to be related to interaction between e1000e module,
drbd and Intel Corporation 82574L Gigabit nic. Each of them works fine
when at least one of the other two is not present.
I edited an udev rule to switch eth1 to eth0 and viceversa. My eth1 is
now Intel Corporation 82579LM Gigabit nic and drbd works so fine...
Thanks anyway
Max
Il 26/08/2013 07:15, [email protected] ha scritto:
Send drbd-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.linbit.com/mailman/listinfo/drbd-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of drbd-user digest..."
Today's Topics:
1. DRDB over Software RAID1 - Failure: (104) Can not open
backing device (Martin Krammer, New Media Interactive)
2. Re: Building DRBD RPM (Patrick Lists)
3. drbd /proc/diskstats counter issue (Justin Albstmeijer)
4. Primary / Unknown (Victor Beliz?rio)
5. initial sync does not start ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Mon, 19 Aug 2013 08:15:35 +0000
From: "Martin Krammer, New Media Interactive" <[email protected]>
Subject: [DRBD-user] DRDB over Software RAID1 - Failure: (104) Can not
open backing device
To: "[email protected]" <[email protected]>
Message-ID:
<f10ae3f83f67734c94ca3b683026cbaa278b9...@db3prd0610mb356.eurprd06.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
I have two webservers running debian 7 (stable) with software RAID1 and DRBD
8.3.11.
On both servers there are the following shares, which should be connected:
On stella: /dev/md4 919014380
204664 872126436 1% /srv
On laura: /dev/md4 442143360
153168996 266514700 37% /srv
Later, the data of laura should be syncronized on /dev/drdb1.
The conf-file looks like:
resource r1 {
on stella {
device /dev/drbd1;
disk /dev/md4;
address 192.168.1.1:7789;
meta-disk /dev/sdb3[0];
}
on laura {
device /dev/drbd1;
disk /dev/md4;
address 192.168.1.2:7789;
meta-disk /dev/sdb2[0];
}
}
If I try to attach...
root@stella:/srv# drbdadm attach r1
--== Thank you for participating in the global usage survey ==--
The server's response is:
node already registered
1: Failure: (104) Can not open backing device.
Command 'drbdsetup 1 disk /dev/md4 /dev/sdb3 0 --set-defaults --create-device
--on-io-error=detach' terminated with exit code 10
Could anybody help me please?
Martin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.linbit.com/pipermail/drbd-user/attachments/20130819/756e9889/attachment.htm>
------------------------------
Message: 2
Date: Mon, 19 Aug 2013 14:19:34 +0200
From: Patrick Lists <[email protected]>
Subject: Re: [DRBD-user] Building DRBD RPM
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 08/19/2013 01:55 PM, Goutam Baul wrote:
Dear List,
We plan to use DRBD 8.4.3 with Redhat Cluster Suit. Our plan is to
replicate data between the Data Center and the Disaster Recovery site
using DRBD while the service at the Data Center run over two nodes as an
active-passive redhat cluster. We have downloaded the drbd-8.4.3.tar.gz
file and tried to build the rpm using the command
./configure --with-km --with-rgmanager --enable-spec --with-distro=redhat
But the drbd-rgmanager rpm is not getting created. The list of rpm
created is
Maybe have a look at the drbd srpm from elrepo.org to see if it gives a
clue. They have been providing drbd rpms for EL6 for a long time.
Regards,
Patrick
------------------------------
Message: 3
Date: Tue, 20 Aug 2013 16:04:32 +0200
From: Justin Albstmeijer <[email protected]>
Subject: [DRBD-user] drbd /proc/diskstats counter issue
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
Hi,
I am monitoring the "# of I/Os currently in progress"
from /proc/diskstats for our drbd devices.
After upgrading from drbd-8.4.1 to drbd-8.4.3 this counter does not seem
to behave as advertised.
Field 9 -- # of I/Os currently in progress
The only field that should go to zero. Incremented as requests are
given to appropriate struct request_queue and decremented as they finish.
It starts at 0 but quickly grows to a value of +4294000000.
It then seems to stabilize on such high number and fluctuates lightly.
The expected behavior is to settle at 0 and lightly fluctuate.
The local underlying disks and dm-* devices show normal counter behavior.
It only seems to impact drbd device counters for which the server it self is
primary.
# while true; do cat /proc/diskstats |grep drbd21 | awk {'print $12'}; sleep
10; done
4294964312
4294964312
4294964312
4294964312
4294964312
4294964312
4294964312
4294964312
4294964312
4294964312
4294964313
4294964312
4294964312
4294964312
4294964312
4294964312
4294964312
4294964312
4294964935
4294964312
Any idea what is happening here?
Currently running:
Centos-6
kernel-2.6.32-358.14.1.el6.x86_64
drbd-kmdl-2.6.32-358.14.1.el6-8.4.3-33.el6.x86_64
Thank you,
Justin
------------------------------
Message: 4
Date: Wed, 21 Aug 2013 22:56:58 +0300
From: Victor Beliz?rio <[email protected]>
Subject: [DRBD-user] Primary / Unknown
To: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Guys,
Please help me.
I'm a production ambient with 2 servers CentOS 6.4 64 bits, and i have instaled
OCFS2 and DRBD 8.3.11, in dual-primary mode. All works fine, file creation,
file update and file delete, so i started the tests:
- reboot the server 01 and check if replication its fine (Ok)- turn off the
power of the server 01 and later turn on, and check if replication is fine
(OK)- reboot the server 02 and 01 simultaneously, and later check if
replication is fine (OK)
Now, i'm in the test with the network. I did a "ifdown eth0" in the server01,
and the cat /proc/drbd are like this :
version: 8.3.11 (api:88/proto:86-96)srcversion: DA5A13F16DE6553FC7CE9B2m:res
cs ro ds p mounted fstype0:tray
WFConnection Primary/Unknown UpToDate/DUnknown C
Ok, its waiting for connection, perfectly. So i turn on again the network, with
ifup eth0 and think the state will be Primary / Primary again. But...not
happens.
I make this test a lot of times, and need to restart the drbd service to work
again Primary / Primary.
Have a way to automatically back the sync of the servers?
Thanks a lot,
Victor
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.linbit.com/pipermail/drbd-user/attachments/20130821/d7817c3e/attachment.htm>
------------------------------
Message: 5
Date: Thu, 22 Aug 2013 14:48:06 +0200 (CEST)
From: "[email protected]"
<[email protected]>
Subject: [DRBD-user] initial sync does not start
To: [email protected]
Message-ID:
<13583485.36681377175686899.JavaMail.defaultUser@defaultHost>
Content-Type: text/plain; charset="utf-8"
Hello,I'm re-posting this message as it is not showing up after 5 days since
the initial post.
I'm (try to) running drbd-8.4.3 on a 3.4.54-8.el6.centos.alt.x86_64 kernel (CentOS6-4
with xen support). I set up my nodes with a resource tier0 resource tier0 { protocol C;
startup { degr-wfc-timeout 120; } net { sndbuf-size 0; } disk {
on-io-error detach; resync-rate 25M; } syncer { rate 25M; al-extents 3833;
verify-alg sha1; } meta-disk internal; on ctb5 { disk /dev/sda3; device
/dev/drbd1; address 172.23.10.1:7799; } on ctb6 { disk /dev/sda3;
device /dev/drbd1; address 172.23.10.2:7799; }Here is the sequence of commands
and status after I zeroed out the partition### Load module, device creation and
"drbdadm up $resource" went ok, leading to the Connected state below[root@ctb5
~]# modprobe drbd[root@ctb5 ~]# drbdadm create-md tier0Writing meta data...initializing
activity logNOT initializing bitmapNew drbd meta data block successfully
created.success[root@ctb5 ~]# cat /proc/drbdversion: 8.4.3 (a
pi
:1/proto:86-101)GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by
root@ctb5, 2013-08-18 15:58:37 1: cs:Connected ro:Secondary/Secondary
ds:Inconsistent/Inconsistent C r----- ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0
ua:0 ap:0 ep:1 wo:f oos:221273604########A this point, I declared ctb5 as the
primary node:[root@ctb5 ~]# drbdadm primary --force tier0[root@ctb5 ~]# cat
/proc/drbdversion: 8.4.3 (api:1/proto:86-101)GIT-hash:
89a294209144b68adb3ee85a73221f964d3ee515 build by root@ctb5, 2013-08-18 15:58:37
1: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r---n- ns:84
nr:0 dw:0 dr:3736 al:0 bm:0 lo:0 pe:1 ua:3 ap:0 ep:1 wo:f oos:221273604
[>....................] sync'ed: 0.1% (216084/216084)M finish: 307:19:28
speed: 0 (0) K/secThe other node (ctb6) is now aware that this node (ctb5) is
primary:[root@ctb6 drbd-8.4.3]# cat /proc/drbdversion: 8.4.3
(api:1/proto:86-101)GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by
root@ctb6, 2013-0
8-1
7 13:13:16 1: cs:SyncTarget ro:Secondary/Primary ds:Inconsistent/UpToDate C r----- ns:0
nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:3 ua:0 ap:0 ep:1 wo:f oos:221273604
[>....................] sync'ed: 0.1% (216084/216084)M finish: 3073:14:40 speed: 0
(0) want: 0 K/secbut nothing is ever written to disk on the secondary node (speed is 0). And
there is "want: 0 K". Why?At last, the loop dialog between the two nodes:drbdsetup
events 11376836259 ST 1,tier0[0] { cs:SyncSource ro:Primary/Secondary
ds:UpToDate/Inconsistent r--- }278 ST-prev 1,tier0[0] { cs:SyncSource ro:Primary/Secondary
ds:UpToDate/Inconsistent r--- }/* long pause here, then */278 ST-new 1,tier0[0] {
cs:NetworkFailure ro:Primary/Unknown ds:UpToDate/Inconsistent r--- }278 ST 1,tier0[0] {
cs:NetworkFailure ro:Primary/Unknown ds:UpToDate/Inconsistent r--- }279 ST-prev 1,tier0[0] {
cs:NetworkFailure ro:Primary/Unknown ds:UpToDate/Inconsistent r--- }279 ST-new 1,tier0[0] {
cs:Unconnected ro:Primary/Unknown ds:UpToDat
e/I
nconsistent r--- }279 ST 1,tier0[0] { cs:WFConnection ro:Primary/Unknown
ds:UpToDate/Inconsistent r--- }280 ST-prev 1,tier0[0] { cs:Unconnected
ro:Primary/Unknown ds:UpToDate/Inconsistent r--- }280 ST-new 1,tier0[0] {
cs:WFConnection ro:Primary/Unknown ds:UpToDate/Inconsistent r--- }280 ST
1,tier0[0] { cs:WFConnection ro:Primary/Unknown ds:UpToDate/Inconsistent r---
}281 ST-prev 1,tier0[0] { cs:WFConnection ro:Primary/Unknown
ds:UpToDate/Inconsistent r--- }281 ST-new 1,tier0[0] { cs:WFReportParams
ro:Primary/Unknown ds:UpToDate/Inconsistent r--- }281 ST 1,tier0[0] {
cs:WFReportParams ro:Primary/Unknown ds:UpToDate/Inconsistent r--- }282 ST-prev
1,tier0[0] { cs:WFReportParams ro:Primary/Unknown ds:UpToDate/Inconsistent r---
}282 ST-new 1,tier0[0] { cs:WFBitMapS ro:Primary/Secondary
ds:UpToDate/Inconsistent r--- }282 ST 1,tier0[0] { cs:WFBitMapS
ro:Primary/Secondary ds:UpToDate/Inconsistent r--- }283 UH 1,tier0[0]
before-resync-source284 UH-post 1,tier0[0] before-resync-sou
rce
0x0000285 ST-prev 1,tier0[0] { cs:WFBitMapS ro:Primary/Secondary
ds:UpToDate/Inconsistent r--- }285 ST-new 1,tier0[0] { cs:SyncSource
ro:Primary/Secondary ds:UpToDate/Inconsistent r--- }285 ST 1,tier0[0] {
cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent r--- }/* another
long pause... */I used a 8.3 conf file for 8.4. Drbd never complained about
anything, so why doesn't it start syncing?Hope someone can help me,
thanks.Massimiliano
Invita i tuoi amici e Tiscali ti premia! Il consiglio di un amico vale pi? di
uno spot in TV. Per ogni nuovo abbonato 30 ? di premio per te e per lui! Un
amico al mese e parli e navighi sempre gratis: http://freelosophy.tiscali.it/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.linbit.com/pipermail/drbd-user/attachments/20130822/84abc6db/attachment.htm>
------------------------------
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
End of drbd-user Digest, Vol 109, Issue 18
******************************************
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
