Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Xiao Ni <xni@redhat.com>
Cc: pmenzel@molgen.mpg.de, ncroxon@redhat.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH v2 1/1] mdadm/udev: Don't handle change event on raw devices
Date: Wed, 4 Jan 2023 18:38:45 -0500	[thread overview]
Message-ID: <a61b4f7e-aded-c40f-c6ee-966e64142c8b@trained-monkey.org> (raw)
In-Reply-To: <20230104162920.18172-1-xni@redhat.com>

On 1/4/23 11:29, Xiao Ni wrote:
> The raw devices are ready when add event happpens and the raid
> can be assembled. So there is no need to handle change events.
> And it can cause some inconvenient problems.
> 
> For example, the OS is installed on md0(/root) and md1(/home).
> md0 and md1 are created on partitions. When it wants to re-install
> OS, anaconda can't clear the storage configure. It deletes one
> partition and does some jobs. The change event happens. Now
> the raid device is assembled again. It can't delete the other
> partitions.
> 
> So in this patch, we don't handle change event on raw devices
> anymore.
> 
> Signed-off-by: Xiao Ni <xni@redhat.com>
> ---
>  udev-md-raid-assembly.rules | 8 ++++++++
>  1 file changed, 8 insertions(+)

Applied!

Thanks,
Jes



      reply	other threads:[~2023-01-04 23:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 16:29 [PATCH v2 1/1] mdadm/udev: Don't handle change event on raw devices Xiao Ni
2023-01-04 23:38 ` Jes Sorensen [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=a61b4f7e-aded-c40f-c6ee-966e64142c8b@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=ncroxon@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --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