From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 0 of 4] Introduction
Date: Mon, 23 Aug 2004 13:10:27 +1000 [thread overview]
Message-ID: <20040823130657.19914.patches@notabene> (raw)
Following are 4 patches for md in 2.6.8.1-mm4
The first three are minor improvements and modifications either
required by or inspired by the fourth.
The fourth adds a new raid personality - raid10. At 56K, I'm not
sure it will get through the mailing list, but interested parties
can find it at:
http://neilb.web.cse.unsw.edu.au/patches/linux-devel/2.6/2004-08-23-03
raid10 provides a combination of raid0 and raid1.
It requires mdadm 1.7.0 or later to use.
The next release of mdadm should have better documention of raid10, but
from the comment in the .c file:
/*
* RAID10 provides a combination of RAID0 and RAID1 functionality.
* The layout of data is defined by
* chunk_size
* raid_disks
* near_copies (stored in low byte of layout)
* far_copies (stored in second byte of layout)
*
* The data to be stored is divided into chunks using chunksize.
* Each device is divided into far_copies sections.
* In each section, chunks are layed out in a style similar to raid0, but
* near_copies copies of each chunk is stored (each on a different drive).
* The starting device for each section is offset near_copies from the starting
* device of the previous section.
* Thus there are (near_copies*far_copies) of each chunk, and each is on a different
* drive.
* near_copies and far_copies must be at least one, and there product is at most
* raid_disks.
*/
raid10 is currently marked EXPERIMENTAL, and this should be taken seriously.
A reasonable amount of basic testing hasn't shown any bugs, and it seems to resync
and rebuild correctly. However wider testing would help.
NeilBrown
next reply other threads:[~2004-08-23 3:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 3:10 NeilBrown [this message]
2004-08-23 3:10 ` [PATCH md 1 of 4] Assorted fixes/improvemnet to generic md resync code NeilBrown
2004-08-23 3:10 ` [PATCH md 4 of 4] RAID10 module for MD NeilBrown
2004-08-23 3:10 ` [PATCH md 2 of 4] Assorted minor md/raid1 fixes NeilBrown
2004-08-23 3:10 ` [PATCH md 3 of 4] Remove most calls to __bdevname from md.c NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2004-09-03 2:20 [PATCH md 0 of 4] Introduction NeilBrown
2004-11-02 3:37 NeilBrown
2005-03-08 5:50 NeilBrown
2005-03-08 6:10 ` Andrew Morton
2005-03-09 3:17 ` Neil Brown
2005-03-09 9:27 ` Mike Tran
2005-03-08 12:49 ` Peter T. Breuer
2005-03-08 17:02 ` Paul Clements
2005-03-08 19:05 ` Peter T. Breuer
2005-03-09 5:07 ` Neil Brown
2005-03-09 15:37 ` Peter T. Breuer
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=20040823130657.19914.patches@notabene \
--to=neilb@cse.unsw.edu.au \
--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