From: NeilBrown <neilb@suse.de>
To: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Create: don't default to bitmap=internal when it is not supported
Date: Mon, 28 Apr 2014 14:19:22 +1000 [thread overview]
Message-ID: <20140428141922.02c361eb@notabene.brown> (raw)
In-Reply-To: <1397548904-31199-1-git-send-email-artur.paszkiewicz@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On Tue, 15 Apr 2014 10:01:44 +0200 Artur Paszkiewicz
<artur.paszkiewicz@intel.com> wrote:
> For large arrays (component size > 100GB) if write-intent bitmap is not
> enabled, then it is set by default to "internal", even if the metadata
> format does support internal bitmaps, which causes Create to fail.
>
> This patch adds checking if add_internal_bitmap is set in the
> superswitch before setting bitmap_file to "internal".
>
> Signed-off-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
> ---
> Create.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Create.c b/Create.c
> index e42627c..602f79c 100644
> --- a/Create.c
> +++ b/Create.c
> @@ -509,6 +509,7 @@ int Create(struct supertype *st, char *mddev,
>
> if (!s->bitmap_file &&
> s->level >= 1 &&
> + st->ss->add_internal_bitmap &&
> (s->write_behind || s->size > 100*1024*1024ULL)) {
> if (c->verbose > 0)
> pr_err("automatically enabling write-intent bitmap on large array\n");
Applied (at last:-)
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-04-28 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 8:01 [PATCH] Create: don't default to bitmap=internal when it is not supported Artur Paszkiewicz
2014-04-28 4:19 ` NeilBrown [this message]
2014-04-30 11:34 ` Artur Paszkiewicz
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=20140428141922.02c361eb@notabene.brown \
--to=neilb@suse.de \
--cc=artur.paszkiewicz@intel.com \
--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.