Re: Cannot update homehost of an existing array: mdadm: /dev/sda3 has wrong name.

[Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>]

On Sat, 19 Oct 2024 22:14:12 +0200
Marc Haber <mh+linux-raid@zugschlus.de> wrote:

> On Sat, Oct 19, 2024 at 11:03:53AM +0100, Geoff Back wrote:
> > I think instead of --name=realhostname you need --homehost=realhostname
> > here.  
> 
> Thanks for spotting this. It has worked now.
> 
> In the rescue system, the array was then available as /dev/md/md_root.
> Booting the production system, the array became
> /dev/md/realhostname:md_root. mdadm --detail says
> Name : realhostname:md_root  (local to host realhostname)
> 
> Is this how things are supposed to work? I had the impression that the
> host name part of the array name only shows up in /dev/md/ if it DOES
> NOT equal the local host name of the running system?
> 
> Greetings
> Marc
> 

I'm looking into Incremental right now and there is a comment:

	 * 3/ Check if there is a match in mdadm.conf
	 * 3a/ if not, check for homehost match.  If no match, assemble as
	 *    a 'foreign' array.

I believe that this is kind of "foreign" naming for native raid.

You can probably correct it by updating your mdadm.conf or you can update your
homehost to production system hostname.

So yes, it looks like expected, we are highlighting that it is not our MD array.
We need user to acknowledge it by updating conf or updating homehost to
change locality to "local".

Thanks,
Mariusz