From: "Phantazm" <phantazm@phantazm.nu>
To: linux-raid@vger.kernel.org
Subject: Re: [PATCH md 0 of 9] Introduction
Date: Fri, 18 Feb 2005 15:25:35 +0100 [thread overview]
Message-ID: <cv4tne$o06$1@sea.gmane.org> (raw)
In-Reply-To: 20050218111131.790.patches@notabene
Would you recommend to apply this package
http://neilb.web.cse.unsw.edu.au/~neilb/patches/linux-devel/2.6/2005-02-18-00/patch-all-2005-02-18-00
To a 2.6.10 kernel?
Thank you for a bery good raid tool :)
"NeilBrown" <neilb@cse.unsw.edu.au> skrev i meddelandet
news:20050218111131.790.patches@notabene...
>
> 9 patches for md in 2.6.11-rc3-mm2 follow.
>
> 1 - tightens up some locking to close a race that is extremely unlikely
> to happen (famous last words). It can only happen when failed devices
> are
> being removed.
> 2 - Fixes a resync related problem for raid5 and raid6 arrays that have
> lost more devices than they can cope with.
> 3 - Fixes a clumsy test that has very little real effect (just a printk).
>
> These three can be considered stable.
>
> 4,5 Improve handling of 'safemode' which is where we mark the superblock
> clean whenever there have been no writes for a little while, and mark
> it dirty before the next write.
> 6-9 Introduce "bitmap based intent logging" which allows a file to
> store - as a bitmap - all block that may have been written recently.
> This allow resync to be optimised, which is more important as drives
> get larger.
>
> These should not be considerred stable - certainly actually using
> the bitmap mode (which requires a 2.0 series version of mdadm) should
> be seen as 'experimental'.
>
> mdadm-2.0-devel-1 was released today.
>
> NeilBrown
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2005-02-18 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 0:40 [PATCH md 0 of 9] Introduction NeilBrown
2005-02-18 0:40 ` [PATCH md 7 of 9] Optimised resync using Bitmap based intent logging NeilBrown
2005-02-18 0:40 ` [PATCH md 5 of 9] Improve locking on 'safemode' and move superblock writes NeilBrown
2005-02-18 0:40 ` [PATCH md 8 of 9] raid1 support for bitmap intent logging NeilBrown
2005-02-18 0:40 ` [PATCH md 3 of 9] Remove kludgy level check from md.c NeilBrown
2005-02-18 0:40 ` [PATCH md 1 of 9] Remove possible oops in md/raid1 NeilBrown
2005-02-18 0:40 ` [PATCH md 9 of 9] Optimise reconstruction when re-adding a recently failed drive NeilBrown
2005-02-18 0:51 ` Mike Hardy
2005-02-18 0:58 ` Neil Brown
2005-02-18 0:40 ` [PATCH md 6 of 9] Improve the interface to sync_request NeilBrown
2005-02-18 0:40 ` [PATCH md 4 of 9] Merge md_enter_safemode into md_check_recovery NeilBrown
2005-02-18 0:40 ` [PATCH md 2 of 9] Make raid5 and raid6 robust against failure during recovery NeilBrown
2005-02-18 14:25 ` Phantazm [this message]
2005-02-20 22:55 ` [PATCH md 0 of 9] Introduction 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='cv4tne$o06$1@sea.gmane.org' \
--to=phantazm@phantazm.nu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.