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] Re: [DRBD-cvs] svn commit by phil - r1985 - branches/drbd-0.7/drbd - Fixed a self made SMP lockup; showing up in drbd_al_com
Date: Mon, 17 Oct 2005 16:15:43 +0200	[thread overview]
Message-ID: <20051017141543.GB32693@barkeeper1.linbit> (raw)
In-Reply-To: <20051017135748.GU8354@marowsky-bree.de>

/ 2005-10-17 15:57:49 +0200
\ Lars Marowsky-Bree:
> On 2005-10-17T15:56:18, Lars Ellenberg <Lars.Ellenberg@linbit.com> wrote:
> 
> > it will be hit. rating is CRITICAL (for smp).
> > 
> > there will be a 0.7.14 today, latest tomorrow, including this fix,
> > and the fix for not notifying the peer about "io-error on read".
> 
> Great, thank you. I'll pull that into SLES9 then.

besser is das.

it is a race, and it will only trigger if you have seriously high
application io load during drbd resync on a Primary/SyncSource.

But yes, SLES9 SMP systems probably will match that description most of
the time, and if you then reconnect the secondary after some downtime ...

-- 
: Lars Ellenberg                                  Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :

      reply	other threads:[~2005-10-17 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051017134012.CB1741431D@mail.linbit.com>
2005-10-17 13:43 ` [Drbd-dev] Re: [DRBD-cvs] svn commit by phil - r1985 - branches/drbd-0.7/drbd - Fixed a self made SMP lockup; showing up in drbd_al_com Lars Marowsky-Bree
2005-10-17 13:56   ` Lars Ellenberg
2005-10-17 13:57     ` Lars Marowsky-Bree
2005-10-17 14:15       ` 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=20051017141543.GB32693@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