From: NeilBrown <neilb@suse.com>
To: Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: report a bug that panic when grow size for external bitmap
Date: Thu, 31 Aug 2017 13:30:31 +1000 [thread overview]
Message-ID: <87efrsfm7c.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <2d737c2f-69f4-672f-2b7c-4a279f70c3c3@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
On Thu, Aug 31 2017, Zhilong Liu wrote:
> On 08/31/2017 08:27 AM, NeilBrown wrote:
>> On Wed, Aug 30 2017, Zhilong Liu wrote:
>>
>>> On 08/29/2017 06:47 PM, NeilBrown wrote:
>>>> Thanks. I see what I missed. Please try this patch instead.
>>> Hi, Neil;
>>> I have tested the following patch, I still got the call-trace after
>>> I built with it.
>>> If you need other infos, I would append.
>>
>> Thanks for testing.
>> I looked more completely and I think it is easiest just to disable the
>> functionality rather than try to fix it.
>> Resizing the file in the kernel is extra complexity that I don't
>> want to get in to.
>> We could adjust the bitmap chunk size so that the file doesn't
>> need to grow, but it started getting more complicated than I really
>> wanted to deal with.
>> If there is anyone actually using file-backed bitmaps who wants to
>> be able to resize the array without removing the bitmap first, then
>> we can look at the problem again. For now I've sent a patch which
>> just returns an error instead of crashing when someone tries to resize
>> an array with a file-backed bitmap.
>
> Hi, Neil;
> Shall update the "SIZE CHANGES" under "GROW MODE" of man-page for
> resize like following after kernel patch merged?
Good idea, but it isn't just "--grow --size". It is anything that
changes the size of the array, which includes changing the number of
devices in a RAID5 etc. So a more general statement would be better.
NeilBrown
>
> Thanks,
> -Zhilong
>
> diff --git a/mdadm.8.in b/mdadm.8.in
> index e0747fb..f0fd1fc 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -2758,6 +2758,11 @@ Also the size of an array cannot be changed while
> it has an active
> bitmap. If an array has a bitmap, it must be removed before the size
> can be changed. Once the change is complete a new bitmap can be created.
>
> +.PP
> +Note:
> +.B "--grow --size"
> +is not yet supported for external file bitmap.
> +
> .SS RAID\-DEVICES CHANGES
>
> A RAID1 array can work with any number of devices from 1 upwards
>
>> Thanks,
>> NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-08-31 3:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 9:37 report a bug that panic when grow size for external bitmap Zhilong Liu
[not found] ` <87y3q3gq8g.fsf@notabene.neil.brown.name>
2017-08-29 2:37 ` Zhilong Liu
2017-08-29 3:12 ` NeilBrown
2017-08-29 4:39 ` Zhilong Liu
2017-08-29 10:47 ` NeilBrown
2017-08-30 2:52 ` Zhilong Liu
2017-08-30 4:08 ` NeilBrown
2017-08-30 4:57 ` Zhilong Liu
2017-08-31 0:27 ` NeilBrown
2017-08-31 2:57 ` Zhilong Liu
2017-08-31 3:30 ` NeilBrown [this message]
2017-09-01 9:49 ` Zhilong Liu
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=87efrsfm7c.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=zlliu@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 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).