[DRBD-user] BrokenPipe Error in drbd

Lars Ellenberg lars.ellenberg at linbit.com
Thu May 3 14:25:43 CEST 2007

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Wed, May 02, 2007 at 07:08:06PM +0530, Shrinivasan wrote:
> Friends.
> 
> I configured DRBD.
> 
> I stopped the Secondary.
> 
> For long time, The primary was working well.
> 
> But, recently, the drbd status show as the following.

Why, oh why, did you withhold the first two lines
with the version information?
in case this is not 0.7.22 (or 23, anyways),
upgrade, reproduce, and report back.

if this is already the most recent 0.7,
maybe I need to ask a few more questions.

> 0: cs:WFConnection st:Primary/Unknown ld:Consistent
>     ns:0 nr:0 dw:52568 dr:278109 al:21 bm:21 lo:0 pe:0 ua:0 ap:0
>  1: cs:WFConnection st:Primary/Unknown ld:Consistent
>     ns:0 nr:0 dw:136676 dr:138585 al:15678 bm:15678 lo:0 pe:0 ua:0 ap:0
>  2: cs:WFConnection st:Primary/Unknown ld:Consistent
>     ns:0 nr:0 dw:18968 dr:62789 al:0 bm:0 lo:0 pe:0 ua:0 ap:0

>  3: cs:BrokenPipe st:Primary/Unknown ld:Inconsistent
>     ns:133816 nr:0 dw:7312 dr:155249 al:1819 bm:2926 lo:0 pe:2095 ua:1430 ap:0


so this is no longer connected, its local data is not consistent,
but it is Primary.  meaning you have a Primary, without access to good
data. typical behaviour of drbd 0.7 in that case would have been to
comit suicide (panic the kernel)... but aparently you configured it
otherwise, or the panic did not work as expected.

and it has no local io pending, but it has some pending data requests
and some unacked data requests for the peer...

this contradicts your statement "it was working well for a long time
[without the other node], only recently it shows something different".

because, if there was no Secondary "since a long time",
the Primary cannot possibly suddenly send requests to it.
it would first need to do the handshake and resync.

so these pieces do not fit together.
you should look through your kernel logs and see if you can find
information correlated to drbd, to the network, or to the io subsystem.
any io-errors, bugs, oopses, dying hard disks, etc.

>  4: cs:Unconfigured
>  5: cs:StandAlone st:Primary/Unknown ld:Consistent
>     ns:0 nr:0 dw:14576 dr:8657 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
>  6: cs:StandAlone st:Primary/Unknown ld:Consistent
>     ns:0 nr:0 dw:709880 dr:7592109 al:2 bm:2 lo:0 pe:0 ua:0 ap:0
>  7: cs:StandAlone st:Primary/Unknown ld:Consistent
>     ns:0 nr:0 dw:320180 dr:174697 al:3 bm:3 lo:0 pe:0 ua:0 ap:0
> 
> 
> 
> the 3rd drbd device is mounted but it is read-only.
> 
> What happened to that partition?
> What I have to do?
> 
> Guide me.

-- 
: Lars Ellenberg                            Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :
__
please use the "List-Reply" function of your email client.



More information about the drbd-user mailing list