From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Just a thought - linux raid wiki - raid 5 grows getting stuck at 0%
Date: Wed, 16 Nov 2016 23:51:01 +0000 [thread overview]
Message-ID: <582CF0E5.2030605@youngman.org.uk> (raw)
I've just been doing a bit of work on the wiki when I put 2 and 2
together, and hope I haven't made 5 ...
Bitmaps interfere with grow operations, I believe ...
And mdadm has recently been modified so that bitmaps are switched on by
default, I also believe ...
Could this be silently blocking the grow, so you don't get any error and
it just sits there doing nothing?
But that brings up two points. Should mdadm now explicitly look for a
bitmap when growing an array, and warn that the bitmap needs to be
disabled? Apparently it currently comes up with some errors that hint at
the cause rather than explicitly say so.
And secondly, I'm sure someone sent an email to the list that explained
when a bitmap was created. I can't find it in my archives. The man page
says it's created if the array is over 100G, but I'm sure the email gave
rather more detail than that and that the figure actually varied.
But I'm sure you can see from this that I'm updating this bit of the
wiki. Is there anything else I ought to know about bitmaps, so I can
document it? :-)
Cheers,
Wol
next reply other threads:[~2016-11-16 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 23:51 Wols Lists [this message]
2016-11-17 6:18 ` Just a thought - linux raid wiki - raid 5 grows getting stuck at 0% NeilBrown
2016-11-17 9:14 ` Wols Lists
2016-11-17 22:54 ` 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=582CF0E5.2030605@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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.