From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 000 of 3] md: Introduction
Date: Thu, 2 Feb 2006 17:02:01 +1100 [thread overview]
Message-ID: <20060202165638.15890.patches@notabene> (raw)
Three patches for 2.6.lastest. All should go in 2.6.16.
One won't apply against -rc1-git5 as it fixes a bug in a patch
in -mm that hasn't quite got to -linus yes.
They are mostly little fixes. I've been doing some more testing,
particularly creating a raid1 over 2 6TB arrays. This requires
version-1 superblocks, so they have had a bit more testing too.
(No, I didn't try to resync the 6TB raid1. I created it
--assume-clean and gave it a write-intent bitmap so a full resync
would never be needed. If one side died, a recovery would take
ages!!!! but for me it was only an experiment, not a serious configuration).
(You will need mdadm-2.3 if you too want a 6TB raid1).
[PATCH 001 of 3] md: Handle overflow of mdu_array_info_t->size better.
[PATCH 002 of 3] md: Assorted little md fixes:
[PATCH 003 of 3] md: Make sure rdev->size gets set for version-1 superblocks.
next reply other threads:[~2006-02-02 6:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 6:02 NeilBrown [this message]
2006-02-02 6:02 ` [PATCH 001 of 3] md: Handle overflow of mdu_array_info_t->size better NeilBrown
2006-02-02 6:02 ` [PATCH 002 of 3] md: Assorted little md fixes: NeilBrown
2006-02-02 6:02 ` [PATCH 003 of 3] md: Make sure rdev->size gets set for version-1 superblocks NeilBrown
2006-02-02 16:47 ` [PATCH 000 of 3] md: Introduction Mr. James W. Laferriere
2006-02-02 21:53 ` Neil Brown
2006-02-03 0:52 ` Mr. James W. Laferriere
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=20060202165638.15890.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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).