From: Xiao Ni <xni@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: Jes Sorensen <jes.sorensen@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
Date: Tue, 27 Oct 2015 02:24:17 -0400 (EDT) [thread overview]
Message-ID: <1369719330.43095568.1445927057223.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <877fm9dy5i.fsf@notabene.neil.brown.name>
----- Original Message -----
> From: "Neil Brown" <neilb@suse.de>
> To: "Xiao Ni" <xni@redhat.com>
> Cc: "Jes Sorensen" <jes.sorensen@redhat.com>, linux-raid@vger.kernel.org
> Sent: Tuesday, October 27, 2015 7:10:17 AM
> Subject: Re: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0
>
> On Mon, Oct 26 2015, Xiao Ni wrote:
>
> >>
> >
> > Thanks for printing out the mistake. I checked the nearby code and found
> > I missed close the cfd. Is this I missed? But I'm wondering that it doesn't
> > close it in the following code. Now it's just closed when it's failed to
> > reshape raid1/raid10 to raid0.
>
> That is a very sensible question to ask - thanks.
> After a quick look - it does seem very strange. That handling of 'cfd'
> and 'fd' seems quite odd.
>
> If you would like to work out what should happen and find a simple way
> to fix the code, that would be great. But I don't insist.
I'll try it and re-send a patch then.
>
> The patch below is quite acceptable as it is a simple solution to a
> simple problem and appear consistent with nearby code. So if you gave
> it a proper description, formatted it properly and posted it in a way
> that didn't mess up all the white space, I would very likely accept it.
>
> However:
> - maybe we should just remove the bitmap rather than complain if we
> find one. After all, we are removing other things (extra devices).
> A raid0 can never had a bitmap, so when converting to a raid0, it
> does make sense to remove the bitmap.
Yes, :) it's better to remove the bitmap than check it.
>
> - The test you used only checks for an internal bitmap, not an external
> one. External bitmaps are hardly ever used except by people who know
> exactly what they are doing, so I'm not too fussed about handling
> them perfectly, but testing for and removing an external bitmap
> might make sense.
>
> Thanks,
> NeilBrown
As you said, I haven't used external bitmaps before. I'll check how to handle
them and add it to the patch too.
Best Regards
Xiao
next prev parent reply other threads:[~2015-10-27 6:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1445751362-15677-1-git-send-email-xni@redhat.com>
2015-10-25 5:38 ` Fwd: [PATCH] mdadm: Check bitmap first when reshape raid1 to raid0 Xiao Ni
2015-10-25 20:21 ` Neil Brown
2015-10-26 12:25 ` Xiao Ni
2015-10-26 23:10 ` Neil Brown
2015-10-27 6:24 ` Xiao Ni [this message]
2015-11-03 0:25 [PATCH] mdadm: check " Xiao Ni
2015-11-21 1:47 ` Xiao Ni
2015-12-21 2:47 ` NeilBrown
2015-12-21 6:00 ` Xiao Ni
-- strict thread matches above, loose matches on Subject: below --
2015-11-02 15:18 Xiao Ni
2015-11-02 16:04 ` Xiao Ni
[not found] <1445589144-12157-1-git-send-email-xni@redhat.com>
2015-10-23 20:35 ` [PATCH] mdadm: Check " Jes Sorensen
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=1369719330.43095568.1445927057223.JavaMail.zimbra@redhat.com \
--to=xni@redhat.com \
--cc=jes.sorensen@redhat.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 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.