From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] DRBD8: Panic in drbd_bm_write_sect() after an io error during resync.
Date: Thu, 15 Feb 2007 16:28:18 +0100 [thread overview]
Message-ID: <200702151628.18909.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C45439C8F9@EXNA.corp.stratus.com>
Am Mittwoch, 14. Februar 2007 19:03 schrieb Montrose, Ernest:
> Hi all,
> We are overwelmed with panic's after io errors. Seem mdev->bc is null
> due to some race condition. Here is one instance:
>
> Two node cluster, node A and Node B. Syncsource is node A. While syncing
> Reads are issued on Node B. I/O errosrs start to occur
> on node A, Node A panics :
>
[...OOPS... ]
Hi Ernest,
I was not able to understand the cause of the oops on the first
glance.
Could you provide the output of ksymoops when you feed this
OOPS to it ? ( I am interested in the disassebled code)
AND
I do this debugging by comparing it to the assembler output
of the compiler.
Please provide the .s files from the machine where you build
your drbd (with your compiler, kernel config and kernel source).
Remke DRBD with "make V=1"
The create the .s file:
Replaceing the "-c" option with "-gstabs+ -S" and the -o "foo.o" to
-o "foo.s" in the call of the compiler
Something like this:
(cd $KDIR ; gcc ... /some/path/foo.c )
Thanks,
Philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
prev parent reply other threads:[~2007-02-15 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 18:03 [Drbd-dev] DRBD8: Panic in drbd_bm_write_sect() after an io error during resync Montrose, Ernest
2007-02-15 15:28 ` Philipp Reisner [this message]
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=200702151628.18909.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-dev@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox