From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Earl Chew <earl.chew@yahoo.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm --create vs --update with --homehost <ignore>
Date: Mon, 12 Feb 2024 16:19:55 +0100 [thread overview]
Message-ID: <20240212161845.00005b28@linux.intel.com> (raw)
In-Reply-To: <4325d3bb-a6d8-4d13-95b6-4f29db1a5206@yahoo.ca>
On Sun, 11 Feb 2024 09:13:10 -0800
Earl Chew <earl.chew@yahoo.ca> wrote:
> Processing of --update blocks removal of homehost from existing arrays even
> though new arrays can be created without an embedded homehost.
>
> Is there any concern allowing --update to remove of homehost from existing
> arrays?
I don't see any issue in making it possible so you need to try. I'm also fine
with removing homehost at all but I would like to hear native experienced user
opinion first.
Thanks,
Mariusz
prev parent reply other threads:[~2024-02-12 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4325d3bb-a6d8-4d13-95b6-4f29db1a5206.ref@yahoo.ca>
2024-02-11 17:13 ` mdadm --create vs --update with --homehost <ignore> Earl Chew
2024-02-12 15:19 ` Mariusz Tkaczyk [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=20240212161845.00005b28@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=earl.chew@yahoo.ca \
--cc=linux-raid@vger.kernel.org \
/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).