Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [DRBD-8.0 PATCH] One more place where stop=sync flag is not explicitely
Date: Mon, 14 Jan 2008 10:21:43 +0100	[thread overview]
Message-ID: <20080114092143.GJ5715@barkeeper1.linbit> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B3767107C5AF6F@EXNA.corp.stratus.com>

On Fri, Jan 11, 2008 at 10:31:31AM -0500, Graham, Simon wrote:
> The following patch fixes an issue where the STOP-SYNC flag was not explicitly
> cleared when resync is required – this can lead to the resync stalling.

probably correct.
though maybe it is not the right place to do it,
it certainly makes it more robust.


-- 
: Lars Ellenberg                            Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :

      reply	other threads:[~2008-01-14  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 15:31 [Drbd-dev] [DRBD-8.0 PATCH] One more place where stop=sync flag is not explicitely Graham, Simon
2008-01-14  9:21 ` Lars Ellenberg [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=20080114092143.GJ5715@barkeeper1.linbit \
    --to=lars.ellenberg@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