linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: NeilBrown <neilb@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mike Accetta <maccetta@laurelnetworks.com>,
	stable@kernel.org
Subject: Re: [PATCH 000 of 2] md: Introduction - bugfixes for md/raid{1,10}
Date: Tue, 12 Jun 2007 13:04:46 -0400	[thread overview]
Message-ID: <466ED22E.8050506@tmr.com> (raw)
In-Reply-To: <20070612110634.25171.patches@notabene>

NeilBrown wrote:
> Following are a couple of bugfixes for raid10 and raid1.  They only
> affect fairly uncommon configurations (more than 2 mirrors) and can
> cause data corruption.  Thay are suitable for 2.6.22 and 21-stable.
>
> Thanks,
> NeilBrown
>
>
>  [PATCH 001 of 2] md: Fix two raid10 bugs.
>  [PATCH 002 of 2] md: Fix bug in error handling during raid1 repair.

I don't know about uncommon, given that I have six machines in this 
building with three way RAID-1 for the boot partition, to be sure I can 
get off the ground enough to get the other partitions up.

And since you added "write-mostly" for remote mirrors I do have a few 
systems doing >2 mirrors as well. This set of patches definitely will be 
in my kernel by this afternoon.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      parent reply	other threads:[~2007-06-12 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  1:09 [PATCH 000 of 2] md: Introduction - bugfixes for md/raid{1,10} NeilBrown
2007-06-12  1:09 ` [PATCH 001 of 2] md: Fix two raid10 bugs NeilBrown
2007-06-12  1:09 ` [PATCH 002 of 2] md: Fix bug in error handling during raid1 repair NeilBrown
2007-06-12 17:04 ` Bill Davidsen [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=466ED22E.8050506@tmr.com \
    --to=davidsen@tmr.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=maccetta@laurelnetworks.com \
    --cc=neilb@suse.de \
    --cc=stable@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).