linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: "Ed L. Cashin" <ecashin@coraid.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: md bitmaps on 2.6.16.y
Date: Thu, 29 Mar 2007 16:27:15 +1000	[thread overview]
Message-ID: <17931.23619.480126.872286@notabene.brown> (raw)
In-Reply-To: message from Ed L. Cashin on Monday March 26

On Monday March 26, ecashin@coraid.com wrote:
> I have been testing an md RAID 1 created using mdadm 2.6.1 on a
> 2.6.16.35 kernel, and the initial results are encouraging.  (The
> 2.6.16.y kernel is a long-term stable branch, unlike most stable
> kernels, which are maintained only until the next stable branch
> becomes active.)
> 
> I see bitmap-related patches with fixes for later kernels being
> discussed in the linux-raid mailing list, but I do not see
> bitmap-related patches in the ChangeLogs for the 2.6.16.y kernel.  My
> hope is that these fixes are only part of the natural churn in the
> newer kernel branches and are not needed for the 2.6.16.y kernels.
> 
> Are there any known issues that would make the use of md bitmaps in a
> 2.6.16.y kernel problematic?  I do see an important RAID 1 fix in
> 2.6.16.40, so I know that 2.6.16.35 isn't good enough.


While I try to remember to back-port any significant and relevant
bugfixes to 2.6.16, I do forget sometimes.. and 2.6.16 isn't really my
focus of development.

If you would like to generate a list of bitmap bugfixes in later
kernels, I could check and let you know how relevant they are for
2.6.16.

NeilBrown

      reply	other threads:[~2007-03-29  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 17:27 md bitmaps on 2.6.16.y Ed L. Cashin
2007-03-29  6:27 ` Neil Brown [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=17931.23619.480126.872286@notabene.brown \
    --to=neilb@suse.de \
    --cc=ecashin@coraid.com \
    --cc=linux-raid@vger.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).