linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
To: Zhao Heming <heming.zhao@suse.com>,
	linux-raid@vger.kernel.org, song@kernel.org, xni@redhat.com
Cc: lidong.zhong@suse.com, neilb@suse.de, colyli@suse.de,
	stable@vger.kernel.org
Subject: Re: [PATCH v4 2/2] md/cluster: fix deadlock when node is doing resync job
Date: Mon, 30 Nov 2020 03:31:09 +0100	[thread overview]
Message-ID: <b120e2b5-f322-6dd2-2b3e-8b7eb7f2bc3d@cloud.ionos.com> (raw)
In-Reply-To: <1605786094-5582-3-git-send-email-heming.zhao@suse.com>



On 11/19/20 12:41, Zhao Heming wrote:
> mkfs.xfs /dev/md0

This would make people think clustered raid can co-work with local fs 
well ...

> mdadm --manage --add /dev/md0 /dev/sdi
> mdadm --wait /dev/md0
> mdadm --grow --raid-devices=3 /dev/md0
> 
> mdadm /dev/md0 --fail /dev/sdg
> mdadm /dev/md0 --remove /dev/sdg
> mdadm --grow --raid-devices=2 /dev/md0

The above is good fit for a new test case in mdadm.

Thanks,
Guoqing

  reply	other threads:[~2020-11-30  2:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 11:41 [PATCH v4 0/2] md/cluster bugs fix Zhao Heming
2020-11-19 11:41 ` [PATCH v4 1/2] md/cluster: block reshape with remote resync job Zhao Heming
2020-11-19 11:41 ` [PATCH v4 2/2] md/cluster: fix deadlock when node is doing " Zhao Heming
2020-11-30  2:31   ` Guoqing Jiang [this message]
2020-11-30  4:16     ` heming.zhao
2020-11-19 11:43 ` [PATCH v4 0/2] md/cluster bugs fix heming.zhao
2020-11-24  1:10 ` Song Liu
  -- strict thread matches above, loose matches on Subject: below --
2020-11-18 16:45 Zhao Heming
2020-11-18 16:45 ` [PATCH v4 2/2] md/cluster: fix deadlock when node is doing resync job Zhao Heming
2020-11-18 16:49   ` heming.zhao
2020-11-18 17:14   ` Greg KH

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=b120e2b5-f322-6dd2-2b3e-8b7eb7f2bc3d@cloud.ionos.com \
    --to=guoqing.jiang@cloud.ionos.com \
    --cc=colyli@suse.de \
    --cc=heming.zhao@suse.com \
    --cc=lidong.zhong@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=song@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xni@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).