From: Andrew Dunn <andrew.g.dunn@gmail.com>
To: tfjellstrom@shaw.ca
Cc: NeilBrown <neilb@suse.de>,
Jon Nelson <jnelson-linux-raid@jamponi.net>,
LinuxRaid <linux-raid@vger.kernel.org>,
pernegger@gmail.com
Subject: Re: unbelievably bad performance: 2.6.27.37 and raid6
Date: Sun, 01 Nov 2009 18:55:24 -0500 [thread overview]
Message-ID: <4AEE1FEC.2090809@gmail.com> (raw)
In-Reply-To: <200911011647.41259.tfjellstrom@shaw.ca>
Thanks for the update Neil, good to have something to look forward to.
I am using Ubuntu 9.10, hopefully the new kernel will be incorporated
sometime in the near future. In the mean time I will back everything up
and create the ARRAY all over again.
Thomas Fjellstrom wrote:
> On Sun November 1 2009, NeilBrown wrote:
>
>> On Mon, November 2, 2009 6:41 am, Thomas Fjellstrom wrote:
>>
>>> On Sun November 1 2009, Andrew Dunn wrote:
>>>
>>>> Are we to expect some resolution in newer kernels?
>>>>
>>> I assume all of the new per-bdi-writeback work going on in .33+ will
>>> have a
>>> large impact. At least I'm hoping.
>>>
>>>
>>>> I am going to rebuild my array (backup data and re-create) to modify
>>>> the chunk size this week. I hope to get a much higher performance when
>>>> increasing from 64k chunk size to 1024k.
>>>>
>>>> Is there a way to modify chunk size in place or does the array need to
>>>> be re-created?
>>>>
>>> This I'm not sure about. I'd like to be able to reshape to a new chunk
>>> size
>>> for testing.
>>>
>> Reshaping to a new chunksize is possible with the latest mdadm and
>> kernel, but I would recommend waiting for mdadm-3.1.1 and 2.6.32.
>> With the current code, a device failure during reshape followed by an
>> unclean shutdown while reshape is happening can lead to unrecoverable
>> data loss. Even a clean shutdown before the shape finishes in that case
>> might be a problem.
>>
>
> That's good to know. Though I'm stuck with 2.6.26 till the performance
> regressions in the io and scheduling subsystems are solved.
>
>
>> 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
>>
>>
>
>
>
--
Andrew Dunn
http://agdunn.net
next prev parent reply other threads:[~2009-11-01 23:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 15:55 unbelievably bad performance: 2.6.27.37 and raid6 Jon Nelson
2009-10-31 18:43 ` Thomas Fjellstrom
2009-11-01 19:37 ` Andrew Dunn
2009-11-01 19:41 ` Thomas Fjellstrom
2009-11-01 23:43 ` NeilBrown
2009-11-01 23:47 ` Thomas Fjellstrom
2009-11-01 23:53 ` Jon Nelson
2009-11-02 2:28 ` Neil Brown
2009-11-01 23:55 ` Andrew Dunn [this message]
2009-11-04 14:43 ` CoolCold
2009-10-31 19:59 ` Christian Pernegger
2009-11-02 19:39 ` Jon Nelson
2009-11-02 20:01 ` Christian Pernegger
2009-11-01 7:17 ` Kristleifur Daðason
2009-11-02 14:54 ` Bill Davidsen
2009-11-02 15:03 ` Jon Nelson
2009-11-03 5:36 ` NeilBrown
2009-11-03 6:09 ` Michael Evans
2009-11-03 6:28 ` NeilBrown
2009-11-03 6:39 ` Michael Evans
2009-11-03 6:46 ` Michael Evans
2009-11-03 9:16 ` NeilBrown
2009-11-03 13:07 ` Goswin von Brederlow
2009-11-03 16:28 ` Michael Evans
2009-11-03 19:26 ` Goswin von Brederlow
2009-11-02 18:51 ` Christian Pernegger
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=4AEE1FEC.2090809@gmail.com \
--to=andrew.g.dunn@gmail.com \
--cc=jnelson-linux-raid@jamponi.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=pernegger@gmail.com \
--cc=tfjellstrom@shaw.ca \
/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).