From: Szymon Madej <szymon.madej@nask.pl>
To: drbd-dev@linbit.com
Subject: Re: [Drbd-dev] Problem with DRBD0.7 on Debian Sarge.
Date: Wed, 21 Dec 2005 09:11:07 +0100 [thread overview]
Message-ID: <43A90E1B.1030204@nask.pl> (raw)
In-Reply-To: <20051220154331.GC5803@soda.linbit>
Thanks for fast answer.
>>kernel: drbd0: Resync done (total 1 sec; paused 0 sec; 0 K/sec)
>>kernel: drbd1: sock_recvmsg returned -14
>>kernel: drbd1: drbd1_receiver [699]: cstate SyncTarget --> BrokenPipe
>>kernel: drbd1: short read receiving data block: read -14 expected 4096
>>kernel: drbd1: error receiving RSDataReply, l: 4112!
>>
>>
>
>you probably hit the bug which was fixed in 0.7.12:
> * Fixed a connection flip-flop bug when the two peers used different
> user provided sizes.
>
>to verify this, first, do "drbdadm disconnect <bad_resource>".
>then "drbdsetup /dev/drbdX show", as well as "cat /proc/partitions",
>on both nodes. compare the results.
>
>
>
And this is the second strange thing. The device sizes are identical on
both nodes:
primary_node# cat /proc/partitions
...
8 8 12048718 sda8
8 9 12851968 sda9
8 10 1004031 sda10
147 0 11917644 drbd0
147 1 12720896 drbd1
secondary_node# cat /proc/partitions
...
8 8 12048718 sda8
8 9 12851968 sda9
8 10 1004031 sda10
147 0 11917644 drbd0
147 1 12720896 drbd1
where drbd0 is built over sda8, drbd1 is built over sda9, sda10 is swap
and sda1-7 are system partitions (/ /usr /home etc.). Is there any
chance that this error could really happen?
And another thing, when secondary went into infinite loop trying to get
drbd1 in sync (every try ended with NetworkError and BrokenPipe) the
drbd1 mounted on primary as /data hanged on listing with "ls -la". The
fast and brutal solution was to disconnect both machines cross link on
eth1 (used by DRBD) and reboot both nodes, and then reconnect them...
but this is not a good method to get HA cluster back to action, isn't
it? :-)
>the solution is probably to either make sure (using some --size
>parameter if possible) that your devices are of the very same size,
>or upgrade to 0.7.15, which should fix the problem.
>
>
>
The company I work in, is using Debian stable tree (currently Sarge, but
some mochines are still Woody) very strictly. Packages which are not
from inside this tree are treated as suspicious, and it is required to
do extensive testing. Sarge provides DRBD in version 0.7.10 and of
course testing it never broke so it was considered stable.. untill
yesterday... but change to 0.7.15 is almost imposible :-(
Tha
next prev parent reply other threads:[~2005-12-21 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 14:49 [Drbd-dev] Problem with DRBD0.7 on Debian Sarge Szymon Madej
2005-12-20 15:43 ` Lars Ellenberg
2005-12-21 8:11 ` Szymon Madej [this message]
2005-12-21 8:56 ` Lars Ellenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43A90E1B.1030204@nask.pl \
--to=szymon.madej@nask.pl \
--cc=drbd-dev@linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.