From: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Create: don't default to bitmap=internal when it is not supported
Date: Wed, 30 Apr 2014 13:34:31 +0200 [thread overview]
Message-ID: <5360DFC7.2040906@intel.com> (raw)
In-Reply-To: <20140428141922.02c361eb@notabene.brown>
On 04/28/2014 06:19 AM, NeilBrown wrote:
> 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
Thanks, but it seems it is not applied yet. I don't see it in the
repository.
Artur
prev parent reply other threads:[~2014-04-30 11:34 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
2014-04-30 11:34 ` Artur Paszkiewicz [this message]
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=5360DFC7.2040906@intel.com \
--to=artur.paszkiewicz@intel.com \
--cc=linux-raid@vger.kernel.org \
--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).