[DRBD-user] "syncer" crash when doing full resync
mkohari at enterasys.com
Wed Sep 22 23:26:18 CEST 2004
I am seeing a drbdd oops almost exact in nature to the one below, certainly looks like memory corruption. It is happening in the same spot (drbd_end_req()).
Because this is happening somewhat consistently within the drbd subsystem and no where else, I wonder if the corruption is coming from within drbd? Was this issue ever resolved?
I am using drbd version 0.6.12, has anyone seen this problem with newer versions of drbd?
From: Philipp Reisner <philipp.reisner at ... <http://gmane.org/get-address.php?address=philipp.reisner%2d63ez5xqkn6DQT0dZR%2bAlfA%40public.gmane.org> >
Subject: Re: [DRBD-user] "syncer" crash when doing full resync <http://news.gmane.org/find-root.php?message_id=%3c200407021711.42767.philipp.reisner%40linbit.com%3e>
Newsgroups: gmane.comp.linux.drbd <http://news.gmane.org/gmane.comp.linux.drbd>
Date: Fri, 02 Jul 2004 17:11:42 +0200
> ohwell :(
After finding time to analyze this problem it is clear that the
peer sent an invalid response-cookie, which caused this node to crash.
We understand what happened there:
-> struct Drbd_Conf* mdev = drbd_conf + MINOR(req->bh->b_rdev);
The crash happens while dereferencing req->bh
The register holding req (%esi) has 0xffffffff .
This req comes from the peer, it got it with the request to write a block.
Either your peer is corrupting its memory (more probabely), or
the node, on which the OOPS happened is corrupting its memory (less
Please go and get new hardware.
[In case memtest86 does not find anything, it could be that the
IO operation to disk does the memory corruption...]
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the drbd-user