From: "Nigel J. Terry" <nigel@nigelterry.net>
To: Mike Hardy <mhardy@h3c.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Raid5 reshape
Date: Mon, 19 Jun 2006 19:33:07 -0400 [thread overview]
Message-ID: <44973433.6020002@nigelterry.net> (raw)
In-Reply-To: <44973371.6060701@h3c.com>
Mike Hardy wrote:
> Unless something has changed recently the parity-rebuild-interrupted /
> restarted-parity-rebuild case shows the same behavior.
>
> It's probably the same chunk of code (I haven't looked, bad hacker!
> bad!), but I thought I'd mention it in case Neil goes looking
>
> The "speed" is truly impressive though. I'll almost be sorry to see it
> fixed :-)
>
> -Mike
> -
> 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
>
>
I'd love to agree about the speed, but this has been the longest 5.8
minutes of my life... :-)
next prev parent reply other threads:[~2006-06-19 23:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 6:34 Raid5 reshape Tim
2006-06-16 6:41 ` Neil Brown
2006-06-16 16:00 ` Nigel J. Terry
2006-06-16 16:14 ` Tim T
2006-06-16 22:28 ` Neil Brown
2006-06-16 22:39 ` Nigel J. Terry
2006-06-16 22:44 ` Neil Brown
2006-06-17 19:21 ` Nigel J. Terry
2006-06-17 21:55 ` Neil Brown
2006-06-17 22:01 ` Nigel J. Terry
2006-06-17 22:05 ` Nigel J. Terry
2006-06-17 22:17 ` Neil Brown
2006-06-17 22:19 ` Nigel J. Terry
2006-06-18 12:57 ` Nigel J. Terry
2006-06-19 2:03 ` Neil Brown
2006-06-19 21:42 ` Nigel J. Terry
2006-06-19 22:46 ` Neil Brown
2006-06-19 22:53 ` Nigel J. Terry
2006-06-19 23:29 ` Mike Hardy
2006-06-19 23:33 ` Nigel J. Terry [this message]
2006-06-19 23:33 ` Neil Brown
2006-06-19 23:35 ` Nigel J. Terry
2006-06-20 10:35 ` Nigel J. Terry
2006-06-21 6:02 ` Neil Brown
2006-06-24 22:58 ` Raid5 reshape (Solved) Nigel J. Terry
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=44973433.6020002@nigelterry.net \
--to=nigel@nigelterry.net \
--cc=linux-raid@vger.kernel.org \
--cc=mhardy@h3c.com \
--cc=neilb@suse.de \
/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).