From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Kinga Tanska <kinga.tanska@linux.intel.com>
Cc: Nigel Croxon <ncroxon@redhat.com>,
linux-raid@vger.kernel.org, jes@trained-monkey.org,
mariusz.tkaczyk@intel.com, kinga.tanska@intel.com
Subject: Re: [PATCH] mdadm reshape hangs on external grow chunk
Date: Wed, 1 Feb 2023 14:37:09 +0100 [thread overview]
Message-ID: <20230201143709.00001086@linux.intel.com> (raw)
In-Reply-To: <20221117150525.00002743@linux.intel.com>
Hi Nigel,
Ping?
Thanks,
Mariusz
On Thu, 17 Nov 2022 15:07:41 +0100
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com> wrote:
> On Thu, 29 Sep 2022 11:35:21 +0200
> Kinga Tanska <kinga.tanska@linux.intel.com> wrote:
>
> > On Fri, 23 Sep 2022 10:26:35 -0400
> > Nigel Croxon <ncroxon@redhat.com> wrote:
> >
> > > After creating a raid array on top of a imsm container. Try to
> > > grow the chunk size and the reshape will hang with zero progress.
> > > The reason is the computation of sync_max_to_set value:
> >
> > Hi Nigel,
> >
> > I was trying to retest with your patch but still have the defect. I
> > analyzed it and found another reason, which causes this defect. In
> > validate_geometry_imsm function freesize and super is being checked and
> > return 1 if any of those is NULL. In my opinion 0 shall be returned
> > here, because it is an error and reshape should be stopped here. I will
> > prepare proper patch and send to review immediately.
> >
> Hi Nigel,
> I agree with Kinga.
> https://patchwork.kernel.org/project/linux-raid/patch/20221028025117.27048-1-kinga.tanska@intel.com/
> Could you please retest the proposed patch on your side and provide feedback?
>
> Thanks,
> Mariusz
next prev parent reply other threads:[~2023-02-01 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:26 [PATCH] mdadm reshape hangs on external grow chunk Nigel Croxon
2022-09-29 9:35 ` Kinga Tanska
2022-11-17 14:07 ` Mariusz Tkaczyk
2023-02-01 13:37 ` Mariusz Tkaczyk [this message]
2023-03-08 19:34 ` 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=20230201143709.00001086@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=jes@trained-monkey.org \
--cc=kinga.tanska@intel.com \
--cc=kinga.tanska@linux.intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@intel.com \
--cc=ncroxon@redhat.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).