From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 000 of 5] Introduction
Date: Tue, 4 Oct 2005 15:23:15 +1000 [thread overview]
Message-ID: <20051004151922.28715.patches@notabene> (raw)
Following are 5 patches that start by adding sysfs support to 'md',
and then proceed to add functionality that makes use if it.
For example:
The raid5 stripe cache can be resized with
echo NNN > /sys/block/mdX/md/raid5/stripe_cache_size
An array can resync'ed with
echo repair > /sys/block/mdX/md/scan_mode
On raid5, the number of parity mismatches found will be reported in
/sys/block/mdX/md/mismatch_cnd
You will note that raid5 has got the most new functionality. Matching
functionality for other md personalities will follow.
These patches should be suitable for merging after 2.6.14 is released.
NeilBrown
[PATCH md 001 of 5] Initial sysfs support for md
[PATCH md 002 of 5] Extend md sysfs support to component devices.
[PATCH md 003 of 5] Add kobject/sysfs support to raid5
[PATCH md 004 of 5] Allow a manual resync with md
[PATCH md 005 of 5] Teach raid5 the difference between 'check' and 'repair'.
next reply other threads:[~2005-10-04 5:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 5:23 NeilBrown [this message]
2005-10-04 5:23 ` [PATCH md 001 of 5] Initial sysfs support for md NeilBrown
2005-10-04 5:23 ` [PATCH md 002 of 5] Extend md sysfs support to component devices NeilBrown
2005-10-11 23:51 ` Andrew Morton
2005-10-04 5:23 ` [PATCH md 003 of 5] Add kobject/sysfs support to raid5 NeilBrown
2005-10-11 23:54 ` Andrew Morton
2005-10-13 5:24 ` Neil Brown
2005-10-04 5:23 ` [PATCH md 004 of 5] Allow a manual resync with md NeilBrown
2005-10-11 23:56 ` Andrew Morton
2005-10-13 5:18 ` Neil Brown
2005-10-11 23:57 ` Andrew Morton
2005-10-04 5:23 ` [PATCH md 005 of 5] Teach raid5 the difference between 'check' and 'repair' NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2005-09-02 6:12 [PATCH md 000 of 5] Introduction 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=20051004151922.28715.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;
as well as URLs for NNTP newsgroup(s).