Mailing List Archive: DRBD: Users

kernel: drbd0: Got NegAck packet. Peer is in troubles?

Index | Next | Previous | View Threaded

KapilKumar.Jain at Emerson

Nov 12, 2009, 11:11 PM

Post #1 of 8 (1379 views)
Permalink

kernel: drbd0: Got NegAck packet. Peer is in troubles?

Hi All,

I got following messages while DHCP is writing to dhcp.leases file, this
file & dhcpd.conf resides in drdb replicated partition.
kernel: drbd0: Got NegAck packet. Peer is in troubles?

After that DHCP is blocked.

I am using drbd version - v0.7.21 & I can not upgrade to latest version.

DRBD configuration from /etc/drbd.conf :

resource r0 {

protocol C;
startup {
wfc-timeout 1;
degr-wfc-timeout 1;
}
disk {
on-io-error pass_on;
}
net {
timeout 60; # 1 seconds (unit = 0.1 seconds)
connect-int 8; # 2 seconds (unit = 1 second)
ping-int 8; # 2 seconds (unit = 1 second)
max-buffers 2048;
ko-count 4;
on-disconnect reconnect;
}
syncer {
rate 16M;
group 2;
al-extents 257;
}
on host1 {
device /dev/drbd0;
disk /dev/hde8;
address 192.168.xx.x:7788;
meta-disk /dev/hde10[0];
}

on HOST_NAME_REMOTE {
device /dev/drbd0;
disk /dev/hde8;
address 192.168.xx.x:7788;
meta-disk /dev/hde10[0];
}
}

Where I should look to resolve the issue?

a) DHCP side which might writing in blocking mode.

b) DRBD side which might not sending proper error code to the upper
levels from lower level.

Thanks in advance.

Regards,
Kapil
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

guohuai_li at hotmail

Nov 13, 2009, 5:27 PM

Post #2 of 8 (1263 views)
Permalink

Re: kernel: drbd0: Got NegAck packet. Peer is in troubles? [In reply to]

i use drbd8.3.0

i also met such problem.

I used msync linux api (sync mode) to write on primary node.

And also it blocks at this case.

regards,

edward.

> Date: Fri, 13 Nov 2009 15:11:55 +0800
> From: KapilKumar.Jain [at] Emerson
> To: drbd-user [at] lists
> Subject: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in troubles?
>
> Hi All,
>
> I got following messages while DHCP is writing to dhcp.leases file, this
> file & dhcpd.conf resides in drdb replicated partition.
> kernel: drbd0: Got NegAck packet. Peer is in troubles?
>
> After that DHCP is blocked.
>
> I am using drbd version - v0.7.21 & I can not upgrade to latest version.
>
> DRBD configuration from /etc/drbd.conf :
>
> resource r0 {
>
> protocol C;
> startup {
> wfc-timeout 1;
> degr-wfc-timeout 1;
> }
> disk {
> on-io-error pass_on;
> }
> net {
> timeout 60; # 1 seconds (unit = 0.1 seconds)
> connect-int 8; # 2 seconds (unit = 1 second)
> ping-int 8; # 2 seconds (unit = 1 second)
> max-buffers 2048;
> ko-count 4;
> on-disconnect reconnect;
> }
> syncer {
> rate 16M;
> group 2;
> al-extents 257;
> }
> on host1 {
> device /dev/drbd0;
> disk /dev/hde8;
> address 192.168.xx.x:7788;
> meta-disk /dev/hde10[0];
> }
>
> on HOST_NAME_REMOTE {
> device /dev/drbd0;
> disk /dev/hde8;
> address 192.168.xx.x:7788;
> meta-disk /dev/hde10[0];
> }
> }
>
> Where I should look to resolve the issue?
>
> a) DHCP side which might writing in blocking mode.
>
> b) DRBD side which might not sending proper error code to the upper
> levels from lower level.
>
> Thanks in advance.
>
> Regards,
> Kapil
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user

_________________________________________________________________
Keep your friends updated¡ªeven when you¡¯re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010

lars.ellenberg at linbit

Nov 16, 2009, 12:42 AM

Post #3 of 8 (1251 views)
Permalink

Re: kernel: drbd0: Got NegAck packet. Peer is in troubles? [In reply to]

On Sat, Nov 14, 2009 at 09:27:12AM +0800, guohuai li wrote:
>
> i use drbd8.3.0

we have 8.3.5 respective 8.3.6 now.

> i also met such problem.
>
> I used msync linux api (sync mode) to write on primary node.
>
> And also it blocks at this case.

In _which_ case does _what_ block,
and what exactly do you mean by "block"?

when "it" "blocks",
I'd like to know what happened up to that point,
have the kernel logs,
cat /proc/drbd
and
ps -eo pid,state,wchan:30,cmd

Thanks.

--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

guohuai_li at hotmail

Nov 16, 2009, 3:34 AM

Post #4 of 8 (1235 views)
Permalink

Re: kernel: drbd0: Got NegAck packet. Peer is in troubles? [In reply to]

Dear lars,

In this case:

now DRBD runs well both on primay node and secondary node.

(Suse linux OS.)

(DRBD-8.3.0, use Protocol C. )

On primary node, one process use linux app "msync"(sync mode) to sync the content to disk.

(And this disk is the block device which DRBD protected.)

Now on the secondary node, the disk has some problem (for example, the disk is pull out from the machine...).

At this very point, the thread will block while calling "msync" api; but, api "fsync" will not be blocked.

( I reproduced this issue in lab, "UpToDate -> Diskless " in /var/log/messages happened at the same time with the time

when "msync" calling is blocked. )

About 3 minutes later, another process is invoked by me, and it will call "msync" api also, but now, it will not be blocked.

So, i think "msync" (sync mode)calling is waiting the OS to tell it that the data is flushed to disk.

But the local disk will not mark the data is flushed to local disk until the remote disk is flushed. (Because DRBD used "Protocol C".)

But at this very point, the remote disk has some problem, (for example, the disk has problem; I reproduded this issue by pulling the disk out ...)

So, "msync" calling is block.

But when DRBD found remore disk is "Diskless", "msync" api will not be blocked.

Because DRBD has the intelligence that remote disk is "Diskless", so it will not check the remore disk to flush data.

And when local disk is flushed, it will mark the data is flushed. So, at this time, "msync" calling will not be blocked.

Would you help to explain it ?

How could I solve this problem ?

Best regards,

Edward

+++++++++++++++++++++++++++++++ in /var/log/messages of primary node ++++++++++++++++++++++++++++++

Nov 16 17:19:27 linux-17 kernel: drbd0: Got NegAck packet. Peer is in troubles?
Nov 16 17:19:27 linux-17 kernel: drbd0: pdsk( UpToDate -> Diskless )
Nov 16 17:19:27 linux-17 kernel: drbd0: Creating new current UUID

+++++++++++++++++++++++++++++++ below is on primary node ++++++++++++++++++++++++++++++++++++++++++++++

linux-17:~ # cat /proc/drbd
version: 8.3.0 (api:88/proto:86-89)
GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by root [at] linux-1, 2009-02-21 11:09:33
0: cs:Connected ro:Primary/Secondary ds:UpToDate/Diskless C r---
ns:1243340 nr:168424 dw:1554336 dr:70703 al:28 bm:63 lo:0 pe:2 ua:0 ap:1 ep:1 wo:b oos:28
1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:53248 dw:6283648 dr:1833 al:3 bm:16 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
2: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:8 dw:11 dr:96 al:1 bm:3 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

> Date: Mon, 16 Nov 2009 09:42:25 +0100
> From: lars.ellenberg [at] linbit
> To: drbd-user [at] lists
> Subject: Re: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in troubles?
>
> On Sat, Nov 14, 2009 at 09:27:12AM +0800, guohuai li wrote:
> >
> > i use drbd8.3.0
>
> we have 8.3.5 respective 8.3.6 now.
>
> > i also met such problem.
> >
> > I used msync linux api (sync mode) to write on primary node.
> >
> > And also it blocks at this case.
>
> In _which_ case does _what_ block,
> and what exactly do you mean by "block"?
>
> when "it" "blocks",
> I'd like to know what happened up to that point,
> have the kernel logs,
> cat /proc/drbd
> and
> ps -eo pid,state,wchan:30,cmd
>
> Thanks.
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
> __
> please don't Cc me, but send to list -- I'm subscribed
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user

_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010

guohuai_li at hotmail

Nov 19, 2009, 10:01 PM

Post #5 of 8 (1180 views)
Permalink

Re: kernel: drbd0: Got NegAck packet. Peer is in troubles? [In reply to]

Hi, dear all,

Now "protocol B" is used, no such issue.

regards,

Edward

From: guohuai_li [at] hotmail
To: lars.ellenberg [at] linbit; drbd-user [at] lists; guohuai_li [at] hotmail; guohuailee0927 [at] gmail
Subject: RE: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in troubles?
Date: Mon, 16 Nov 2009 19:34:12 +0800

Dear lars,

In this case:
now DRBD runs well both on primay node and secondary node.
(Suse linux OS.)
(DRBD-8.3.0, use Protocol C. )

On primary node, one process use linux app "msync"(sync mode) to sync the content to disk.
(And this disk is the block device which DRBD protected.)

Now on the secondary node, the disk has some problem (for example, the disk is pull out from the machine...).
At this very point, the thread will block while calling "msync" api; but, api "fsync" will not be blocked.
( I reproduced this issue in lab, "UpToDate -> Diskless " in /var/log/messages happened at the same time with the time
when "msync" calling is blocked. )

About 3 minutes later, another process is invoked by me, and it will call "msync" api also, but now, it will not be blocked.

So, i think "msync" (sync mode)calling is waiting the OS to tell it that the data is flushed to disk.
But the local disk will not mark the data is flushed to local disk until the remote disk is flushed. (Because DRBD used "Protocol C".)
But at this very point, the remote disk has some problem, (for example, the disk has problem; I reproduded this issue by pulling the disk out ...)
So, "msync" calling is block.
But when DRBD found remore disk is "Diskless", "msync" api will not be blocked.
Because DRBD has the intelligence that remote disk is "Diskless", so it will not check the remore disk to flush data.
And when local disk is flushed, it will mark the data is flushed. So, at this time, "msync" calling will not be blocked.

Would you help to explain it ?
How could I solve this problem ?

Best regards,
Edward

+++++++++++++++++++++++++++++++ in /var/log/messages of primary node ++++++++++++++++++++++++++++++
Nov 16 17:19:27 linux-17 kernel: drbd0: Got NegAck packet. Peer is in troubles?
Nov 16 17:19:27 linux-17 kernel: drbd0: pdsk( UpToDate -> Diskless )
Nov 16 17:19:27 linux-17 kernel: drbd0: Creating new current UUID

+++++++++++++++++++++++++++++++ below is on primary node ++++++++++++++++++++++++++++++++++++++++++++++
linux-17:~ # cat /proc/drbd
version: 8.3.0 (api:88/proto:86-89)
GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by root [at] linux-1, 2009-02-21 11:09:33
0: cs:Connected ro:Primary/Secondary ds:UpToDate/Diskless C r---
ns:1243340 nr:168424 dw:1554336 dr:70703 al:28 bm:63 lo:0 pe:2 ua:0 ap:1 ep:1 wo:b oos:28
1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:53248 dw:6283648 dr:1833 al:3 bm:16 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
2: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:8 dw:11 dr:96 al:1 bm:3 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

> Date: Mon, 16 Nov 2009 09:42:25 +0100
> From: lars.ellenberg [at] linbit
> To: drbd-user [at] lists
> Subject: Re: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in troubles?
>
> On Sat, Nov 14, 2009 at 09:27:12AM +0800, guohuai li wrote:
> >
> > i use drbd8.3.0
>
> we have 8.3.5 respective 8.3.6 now.
>
> > i also met such problem.
> >
> > I used msync linux api (sync mode) to write on primary node.
> >
> > And also it blocks at this case.
>
> In _which_ case does _what_ block,
> and what exactly do you mean by "block"?
>
> when "it" "blocks",
> I'd like to know what happened up to that point,
> have the kernel logs,
> cat /proc/drbd
> and
> ps -eo pid,state,wchan:30,cmd
>
> Thanks.
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
> __
> please don't Cc me, but send to list -- I'm subscribed
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user

Keep your friends updated— even when you’re not signed in.
_________________________________________________________________
Windows Live: Make it easier for your friends to see what you’re up to on Facebook.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009

KapilKumar.Jain at Emerson

Nov 19, 2009, 10:45 PM

Post #6 of 8 (1176 views)
Permalink

Re: kernel: drbd0: Got NegAck packet. Peeris in troubles? [In reply to]

Using protocol B is not appropriate for data consistency. There should
be something done by DRBD while sending/receiving NegAck.

Regards,
Kapil

________________________________

From: drbd-user-bounces [at] lists
[mailto:drbd-user-bounces [at] lists] On Behalf Of guohuai li
Sent: Friday, November 20, 2009 11:31 AM
To: lars.ellenberg [at] linbit; drbd user; guohuailee0927 [at] gmail
Subject: Re: [DRBD-user] kernel: drbd0: Got NegAck packet. Peeris in
troubles?

Hi, dear all,

Now "protocol B" is used, no such issue.

regards,
Edward

________________________________

From: guohuai_li [at] hotmail
To: lars.ellenberg [at] linbit; drbd-user [at] lists;
guohuai_li [at] hotmail; guohuailee0927 [at] gmail
Subject: RE: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in
troubles?
Date: Mon, 16 Nov 2009 19:34:12 +0800

Dear lars,

In this case:
now DRBD runs well both on primay node and secondary node.
(Suse linux OS.)
(DRBD-8.3.0, use Protocol C. )

On primary node, one process use linux app "msync"(sync mode) to sync
the content to disk.
(And this disk is the block device which DRBD protected.)

Now on the secondary node, the disk has some problem (for example, the
disk is pull out from the machine...).
At this very point, the thread will block while calling "msync" api;
but, api "fsync" will not be blocked.
( I reproduced this issue in lab, "UpToDate -> Diskless " in
/var/log/messages happened at the same time with the time
when "msync" calling is blocked. )

About 3 minutes later, another process is invoked by me, and it will
call "msync" api also, but now, it will not be blocked.

So, i think "msync" (sync mode)calling is waiting the OS to tell it that
the data is flushed to disk.
But the local disk will not mark the data is flushed to local disk until
the remote disk is flushed. (Because DRBD used "Protocol C".)
But at this very point, the remote disk has some problem, (for example,
the disk has problem; I reproduded this issue by pulling the disk out
...)
So, "msync" calling is block.
But when DRBD found remore disk is "Diskless", "msync" api will not be
blocked.
Because DRBD has the intelligence that remote disk is "Diskless", so it
will not check the remore disk to flush data.
And when local disk is flushed, it will mark the data is flushed. So, at
this time, "msync" calling will not be blocked.

Would you help to explain it ?
How could I solve this problem ?

Best regards,
Edward

+++++++++++++++++++++++++++++++ in /var/log/messages of primary node
++++++++++++++++++++++++++++++
Nov 16 17:19:27 linux-17 kernel: drbd0: Got NegAck packet. Peer is in
troubles?
Nov 16 17:19:27 linux-17 kernel: drbd0: pdsk( UpToDate -> Diskless )
Nov 16 17:19:27 linux-17 kernel: drbd0: Creating new current UUID

+++++++++++++++++++++++++++++++ below is on primary node
++++++++++++++++++++++++++++++++++++++++++++++
linux-17:~ # cat /proc/drbd
version: 8.3.0 (api:88/proto:86-89)
GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by
root [at] linux-1, 2009-02-21 11:09:33
0: cs:Connected ro:Primary/Secondary ds:UpToDate/Diskless C r---
ns:1243340 nr:168424 dw:1554336 dr:70703 al:28 bm:63 lo:0 pe:2 ua:0
ap:1 ep:1 wo:b oos:28
1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:53248 dw:6283648 dr:1833 al:3 bm:16 lo:0 pe:0 ua:0 ap:0 ep:1
wo:b oos:0
2: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:8 dw:11 dr:96 al:1 bm:3 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++

> Date: Mon, 16 Nov 2009 09:42:25 +0100
> From: lars.ellenberg [at] linbit
> To: drbd-user [at] lists
> Subject: Re: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in
troubles?
>
> On Sat, Nov 14, 2009 at 09:27:12AM +0800, guohuai li wrote:
> >
> > i use drbd8.3.0
>
> we have 8.3.5 respective 8.3.6 now.
>
> > i also met such problem.
> >
> > I used msync linux api (sync mode) to write on primary node.
> >
> > And also it blocks at this case.
>
> In _which_ case does _what_ block,
> and what exactly do you mean by "block"?
>
> when "it" "blocks",
> I'd like to know what happened up to that point,
> have the kernel logs,
> cat /proc/drbd
> and
> ps -eo pid,state,wchan:30,cmd
>
> Thanks.
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD(r) and LINBIT(r) are registered trademarks of LINBIT, Austria.
> __
> please don't Cc me, but send to list -- I'm subscribed
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user

________________________________

Keep your friends updated- even when you're not signed in.
<http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-actio
n/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_
5:092010>

________________________________

Windows Live: Make it easier for your friends to see what you're up to
on Facebook.
<http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-actio
n/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_
2:092009>

guohuai_li at hotmail

Nov 29, 2009, 2:30 AM

Post #7 of 8 (997 views)
Permalink

Re: kernel: drbd0: Got NegAck packet. Peeris in troubles? [In reply to]

I agree it is really need some code change for DRBD.

:-)

Is there any new update for this issue ?

regards,

Edward

Subject: RE: [DRBD-user] kernel: drbd0: Got NegAck packet. Peeris in troubles?
Date: Fri, 20 Nov 2009 14:45:10 +0800
From: KapilKumar.Jain [at] Emerson
To: guohuai_li [at] hotmail; lars.ellenberg [at] linbit; drbd-user [at] lists; guohuailee0927 [at] gmail

Using protocol B is not appropriate for data consistency. There should be something done by DRBD while sending/receiving NegAck.

Regards,
Kapil

From: drbd-user-bounces [at] lists [mailto:drbd-user-bounces [at] lists] On Behalf Of guohuai li
Sent: Friday, November 20, 2009 11:31 AM
To: lars.ellenberg [at] linbit; drbd user; guohuailee0927 [at] gmail
Subject: Re: [DRBD-user] kernel: drbd0: Got NegAck packet. Peeris in troubles?

Hi, dear all,

Now "protocol B" is used, no such issue.

regards,
Edward

From: guohuai_li [at] hotmail
To: lars.ellenberg [at] linbit; drbd-user [at] lists; guohuai_li [at] hotmail; guohuailee0927 [at] gmail
Subject: RE: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in troubles?
Date: Mon, 16 Nov 2009 19:34:12 +0800

Dear lars,

In this case:
now DRBD runs well both on primay node and secondary node.
(Suse linux OS.)
(DRBD-8.3.0, use Protocol C. )

On primary node, one process use linux app "msync"(sync mode) to sync the content to disk.
(And this disk is the block device which DRBD protected.)

Now on the secondary node, the disk has some problem (for example, the disk is pull out from the machine...).
At this very point, the thread will block while calling "msync" api; but, api "fsync" will not be blocked.
( I reproduced this issue in lab, "UpToDate -> Diskless " in /var/log/messages happened at the same time with the time
when "msync" calling is blocked. )

About 3 minutes later, another process is invoked by me, and it will call "msync" api also, but now, it will not be blocked.

So, i think "msync" (sync mode)calling is waiting the OS to tell it that the data is flushed to disk.
But the local disk will not mark the data is flushed to local disk until the remote disk is flushed. (Because DRBD used "Protocol C".)
But at this very point, the remote disk has some problem, (for example, the disk has problem; I reproduded this issue by pulling the disk out ...)
So, "msync" calling is block.
But when DRBD found remore disk is "Diskless", "msync" api will not be blocked.
Because DRBD has the intelligence that remote disk is "Diskless", so it will not check the remore disk to flush data.
And when local disk is flushed, it will mark the data is flushed. So, at this time, "msync" calling will not be blocked.

Would you help to explain it ?
How could I solve this problem ?

Best regards,
Edward

+++++++++++++++++++++++++++++++ in /var/log/messages of primary node ++++++++++++++++++++++++++++++
Nov 16 17:19:27 linux-17 kernel: drbd0: Got NegAck packet. Peer is in troubles?
Nov 16 17:19:27 linux-17 kernel: drbd0: pdsk( UpToDate -> Diskless )
Nov 16 17:19:27 linux-17 kernel: drbd0: Creating new current UUID

+++++++++++++++++++++++++++++++ below is on primary node ++++++++++++++++++++++++++++++++++++++++++++++
linux-17:~ # cat /proc/drbd
version: 8.3.0 (api:88/proto:86-89)
GIT-hash: 9ba8b93e24d842f0dd3fb1f9b90e8348ddb95829 build by root [at] linux-1, 2009-02-21 11:09:33
0: cs:Connected ro:Primary/Secondary ds:UpToDate/Diskless C r---
ns:1243340 nr:168424 dw:1554336 dr:70703 al:28 bm:63 lo:0 pe:2 ua:0 ap:1 ep:1 wo:b oos:28
1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:53248 dw:6283648 dr:1833 al:3 bm:16 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
2: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:8 dw:11 dr:96 al:1 bm:3 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

> Date: Mon, 16 Nov 2009 09:42:25 +0100
> From: lars.ellenberg [at] linbit
> To: drbd-user [at] lists
> Subject: Re: [DRBD-user] kernel: drbd0: Got NegAck packet. Peer is in troubles?
>
> On Sat, Nov 14, 2009 at 09:27:12AM +0800, guohuai li wrote:
> >
> > i use drbd8.3.0
>
> we have 8.3.5 respective 8.3.6 now.
>
> > i also met such problem.
> >
> > I used msync linux api (sync mode) to write on primary node.
> >
> > And also it blocks at this case.
>
> In _which_ case does _what_ block,
> and what exactly do you mean by "block"?
>
> when "it" "blocks",
> I'd like to know what happened up to that point,
> have the kernel logs,
> cat /proc/drbd
> and
> ps -eo pid,state,wchan:30,cmd
>
> Thanks.
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
> __
> please don't Cc me, but send to list -- I'm subscribed
> _______________________________________________
> drbd-user mailing list
> drbd-user [at] lists
> http://lists.linbit.com/mailman/listinfo/drbd-user

Keep your friends updated— even when you’re not signed in.

Windows Live: Make it easier for your friends to see what you’re up to on Facebook.
_________________________________________________________________
Windows Live: Keep your friends up to date with what you do online.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010

lars.ellenberg at linbit

Nov 30, 2009, 7:17 AM

Post #8 of 8 (965 views)
Permalink

Re: kernel: drbd0: Got NegAck packet. Peeris in troubles? [In reply to]

On Sun, Nov 29, 2009 at 06:30:27PM +0800, guohuai li wrote:
>
> I agree it is really need some code change for DRBD.

What for, exactly?

> :-)
>
> Is there any new update for this issue ?

The issue that "somehow" mmap, msync and friends don't work,
while write, fsync and friends continue to work fine?

Well. "Works for me."
But maybe I simply don't understand your issue.

So...
you can get LINBIT to come and see and recognize and solve your issue,
(see my .sig)

Or continue to try and figure it out for yourself. Or move on. Or wait
that "somehow" whatever your issue is, it may resolve itself accidentally.

;)

Cheers,

--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads