Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: "Montrose, Ernest" <Ernest.Montrose@stratus.com>
Subject: Re: [Drbd-dev] DRBD8:Panics in lc_find due to null lcafterScsiMEDIUM_ERROR I.O error.
Date: Wed, 7 Feb 2007 13:59:53 +0100	[thread overview]
Message-ID: <200702071359.53872.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C45439C8E1@EXNA.corp.stratus.com>

Am Samstag, 3. Februar 2007 00:27 schrieb Montrose, Ernest:
>  Phil,
> The one spot that was missed is in this patch.  I looked around for
> other places but I am
> Still not that everything is covered.

Hi Ernest,

I decided for a different patch:
http://lists.linbit.com/pipermail/drbd-cvs/2007-February/001460.html

Clearing the bit in the bitmap is valid in this case, we only
must not call drbd_try_clear_on_disk_bm(), since that function
in turn uses mdev->resync. 

The second reason is that there are more calls to the drbd_set_in_sync()
function than to the drbd_try_clear_on_disk_bm(). We would need
to protect each and every call to drbd_set_in_sync()...

-Phil
-- 
: 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 :

  reply	other threads:[~2007-02-07 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 23:27 [Drbd-dev] DRBD8:Panics in lc_find due to null lcafterScsiMEDIUM_ERROR I.O error Montrose, Ernest
2007-02-07 12:59 ` Philipp Reisner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-07 13:08 Montrose, Ernest

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=200702071359.53872.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=Ernest.Montrose@stratus.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