From: Nix <nix@esperi.org.uk>
To: NeilBrown <neilb@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: 4.11.2: reshape raid5 -> raid6 atop bcache deadlocks at start on md_attr_store / raid5_make_request
Date: Wed, 24 May 2017 20:42:48 +0100 [thread overview]
Message-ID: <87d1ayhwhz.fsf@esperi.org.uk> (raw)
In-Reply-To: <87poezhwsa.fsf@notabene.neil.brown.name> (NeilBrown's message of "Wed, 24 May 2017 11:24:21 +1000")
On 24 May 2017, NeilBrown said:
> Alternately, this might do it.
Bingo! Ticking away nicely:
[ 147.538274] md/raid:md125: device sda3 operational as raid disk 0
[ 147.574356] md/raid:md125: device sdd3 operational as raid disk 3
[ 147.586482] md/raid:md125: device sdc3 operational as raid disk 2
[ 147.598571] md/raid:md125: device sdb3 operational as raid disk 1
[ 147.613949] md/raid:md125: raid level 6 active with 4 out of 5 devices, algorithm 18
[ 147.776155] md: reshape of RAID array md125
md125 : active raid6 sda3[0] sdf3[5] sdd3[4] sdc3[2] sdb3[1]
15391689216 blocks super 1.2 level 6, 512k chunk, algorithm 18 [5/4] [UUUU_]
[>....................] reshape = 0.0% (2669056/5130563072) finish=1363.5min speed=62678K/sec
(wow, this is a lot faster: only 1363 min / 70MiB/s, versus the
--backup-file one, for an array half the size, that was >2500 min,
12MiB/s. I mean, yes, it was at the slow end of the disk, but they don't
differ in speed *that* much.)
Machine still perfectly responsive, as if on reshape was happening at
all. (But then, I've got used to that. The last time I saw any md resync-
induced delays was long ago when I had a sym53c75 in the loop with an
I/O rate of 10MiB/s. I think delays are unavoidable with something
that slow in there.)
next prev parent reply other threads:[~2017-05-24 19:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 9:13 4.11.2: reshape raid5 -> raid6 atop bcache deadlocks at start on md_attr_store / raid5_make_request Nix
2017-05-22 11:35 ` NeilBrown
2017-05-22 15:30 ` Nix
2017-05-22 19:07 ` Wols Lists
2017-05-22 20:43 ` Nix
2017-05-23 1:20 ` NeilBrown
2017-05-23 10:10 ` Nix
2017-05-23 1:39 ` NeilBrown
2017-05-23 14:47 ` Wols Lists
2017-05-24 1:50 ` NeilBrown
2017-05-23 1:07 ` NeilBrown
2017-05-22 21:38 ` Nix
2017-05-23 14:16 ` Wols Lists
2017-05-23 15:00 ` Nix
2017-05-24 1:24 ` NeilBrown
2017-05-24 13:28 ` Nix
2017-05-25 1:31 ` NeilBrown
2017-05-25 12:14 ` Nix
2017-05-24 19:42 ` Nix [this message]
2017-05-24 22:57 ` Shaohua Li
2017-05-25 1:30 ` NeilBrown
2017-05-25 1:46 ` Shaohua Li
2017-05-26 3:23 ` NeilBrown
2017-05-26 16:40 ` Shaohua Li
2017-05-28 23:17 ` NeilBrown
2017-05-30 17:41 ` Shaohua Li
2017-06-05 6:49 ` [PATCH] md: fix deadlock between mddev_suspend() and md_write_start() NeilBrown
2017-06-06 0:01 ` Shaohua Li
2017-06-07 1:45 ` NeilBrown
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=87d1ayhwhz.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
/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.