Re: [Patch] mdadm ignoring homehost?

[Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>]

On Mon, Apr 20, 2009 at 03:58:08PM +1000, Neil Brown wrote:
[...]
> If you use 1.x metadata (e.g. 1.0), then this works nicely.
> 
>  mdadm --create /dev/md/foo --metadata 1.0 --level .....
> 
> This will store the name 'foo' in the metadata and when you assemble
> the array, it will be called /dev/md/foo.
> This will be a symlink to /dev/md125 or something like that, but you
> don't need to care.

Does this really work with mdadm 2.6.7.1?

Because I have this from "--examine --scan"

ARRAY /dev/md/boot level=raid1 metadata=1.0 num-devices=2 UUID=edb4254d:4274fac1:dd6cad61:a8e3c347 name=boot

Of course, /dev/mdadm.conf has the same entry.

But:

$> mdadm -A --scan
mdadm: /dev/md/boot does not exist and is not a 'standard' name so it cannot be created

The array was *not* created as you suggested,
but it has metadata 1.0 and a name.
Which name is also returned by --examine --scan
as array device name.

Thanks,

bye,

-- 

piergiorgio