From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 000 of 6] Introduction
Date: Thu, 11 Aug 2005 17:22:26 +1000 [thread overview]
Message-ID: <20050811171720.10115.patches@notabene> (raw)
The following 6 patches for md mostly add some new functionality (hot-adding
write-intent bitmaps and write-behind support for raid1).
They can, and should, wait for after 2.6.13 is released.
The first patch fixes a bug which could be annoying, and is probably
suitable for 2.6.13, however I suspect it is too late for 2.6.13, and
it is ok to be left.
The bug is that if you create an array with an internal bitmap, shut
it down, and then create an array with the same md device, the md
drive will assume it should have a bitmap too. As the array can be
created with a different md device, it is mostly an inconvenience.
I'm pretty sure there is no risk of data corruption.
NeilBrown
[PATCH md 001 of 6] Make sure mddev->bitmap_offset gets cleared between array instantiations.
[PATCH md 002 of 6] Don't allow new md/bitmap file to be set if one already exists
[PATCH md 003 of 6] Improve handling of bitmap initialisation.
[PATCH md 004 of 6] All hot-add and hot-remove of md intent logging bitmaps
[PATCH md 005 of 6] Support write-mostly device in raid1
[PATCH md 006 of 6] Add write-behind support for md/raid1
next reply other threads:[~2005-08-11 7:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 7:22 NeilBrown [this message]
2005-08-11 7:22 ` [PATCH md 002 of 6] Don't allow new md/bitmap file to be set if one already exists NeilBrown
2005-08-11 7:22 ` [PATCH md 001 of 6] Make sure mddev->bitmap_offset gets cleared between array instantiations NeilBrown
2005-08-11 7:22 ` [PATCH md 003 of 6] Improve handling of bitmap initialisation NeilBrown
2005-08-11 7:22 ` [PATCH md 006 of 6] Add write-behind support for md/raid1 NeilBrown
2005-08-12 6:22 ` Al Boldi
2005-08-12 12:15 ` Paul Clements
2005-08-13 5:00 ` Al Boldi
2005-08-14 22:24 ` Neil Brown
2005-08-15 4:45 ` Al Boldi
2005-08-14 22:16 ` Neil Brown
2005-08-11 7:22 ` [PATCH md 004 of 6] All hot-add and hot-remove of md intent logging bitmaps NeilBrown
2005-08-11 7:22 ` [PATCH md 005 of 6] Support write-mostly device in raid1 NeilBrown
2005-08-11 8:51 ` RAID5 spare change djani22
2005-08-11 10:08 ` Neil Brown
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=20050811171720.10115.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