From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 000 of 14] Introduction
Date: Thu, 1 Dec 2005 14:22:47 +1100 [thread overview]
Message-ID: <20051201141508.29384.patches@notabene> (raw)
Following are 14 more patches for md in 2.6.15-rc2-mm1
None are appropriate for 2.6.15 - all should wait for 2.6.16 to open.
With these the handling for read errors by overwriting with correct
data is supported for all relevant raid levels. Also user-requested
checking of redundant information is supported for all levels, and
report the number of affect blocks in sysfs (though this number is
only approximate).
/proc/mdstat becomes pollable so that mdadm can get timely
notification of changes without polling at a high frequency.
There are also a substantial number of code cleanups.
[PATCH md 001 of 14] Support check-without-repair of raid10 arrays
[PATCH md 002 of 14] Allow raid1 to check consistency
[PATCH md 003 of 14] Make sure read error on last working drive of raid1 actually returns failure.
[PATCH md 004 of 14] auto-correct correctable read errors in raid10
[PATCH md 005 of 14] raid10 read-error handling - resync and read-only
[PATCH md 006 of 14] Make /proc/mdstat pollable.
[PATCH md 007 of 14] Clean up 'page' related names in md
[PATCH md 008 of 14] Convert md to use kzalloc throughout
[PATCH md 009 of 14] Tidy up raid5/6 hash table code.
[PATCH md 010 of 14] Convert various kmap calls to kmap_atomic
[PATCH md 011 of 14] Convert recently exported symbol to GPL
[PATCH md 012 of 14] Break out of a loop that doesn't need to run to completion.
[PATCH md 013 of 14] Remove personality numbering from md.
[PATCH md 014 of 14] Fix possible problem in raid1/raid10 error overwriting.
next reply other threads:[~2005-12-01 3:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 3:22 NeilBrown [this message]
2005-12-01 3:22 ` [PATCH md 001 of 14] Support check-without-repair of raid10 arrays NeilBrown
2005-12-01 3:22 ` [PATCH md 002 of 14] Allow raid1 to check consistency NeilBrown
2005-12-01 22:34 ` Andrew Morton
2005-12-05 23:30 ` Neil Brown
2005-12-06 3:50 ` Andrew Morton
2005-12-01 3:23 ` [PATCH md 003 of 14] Make sure read error on last working drive of raid1 actually returns failure NeilBrown
2005-12-01 3:23 ` [PATCH md 004 of 14] auto-correct correctable read errors in raid10 NeilBrown
2005-12-01 3:23 ` [PATCH md 005 of 14] raid10 read-error handling - resync and read-only NeilBrown
2005-12-01 3:23 ` [PATCH md 006 of 14] Make /proc/mdstat pollable NeilBrown
2005-12-01 22:39 ` Andrew Morton
2005-12-01 3:23 ` [PATCH md 007 of 14] Clean up 'page' related names in md NeilBrown
2005-12-01 3:23 ` [PATCH md 008 of 14] Convert md to use kzalloc throughout NeilBrown
2005-12-01 22:42 ` Andrew Morton
2005-12-01 3:23 ` [PATCH md 009 of 14] Tidy up raid5/6 hash table code NeilBrown
2005-12-01 3:23 ` [PATCH md 010 of 14] Convert various kmap calls to kmap_atomic NeilBrown
2005-12-01 22:46 ` Andrew Morton
2005-12-05 23:43 ` Neil Brown
2005-12-01 3:23 ` [PATCH md 011 of 14] Convert recently exported symbol to GPL NeilBrown
2005-12-01 3:23 ` [PATCH md 012 of 14] Break out of a loop that doesn't need to run to completion NeilBrown
2005-12-01 3:23 ` [PATCH md 013 of 14] Remove personality numbering from md NeilBrown
2005-12-01 3:24 ` [PATCH md 014 of 14] Fix possible problem in raid1/raid10 error overwriting NeilBrown
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=20051201141508.29384.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@osdl.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