Re: [Patch] mdadm ignoring homehost?

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

On Sat, Apr 18, 2009 at 12:19:54PM +0200, Luca Berra wrote:
> i believe the num-devices is redundant since this value is already
> stored in the superblock

I believe too. As I mentioned, it would be possible
to edit the outcome of "--examine --scan", but not
really wanted.

> we could change the way mdadm outputs data to put _all_ redundant
> information in subsequent lines and keep the only required info in the
> 'ARRAY' line,
> so mdadm --examine --scan | grep ARRAY would be suitable for initial
> configuration
> or even print it only if a --verbose flag is added
> so mdadm --examine --scan by itself would suit most need

This second option I would prefer in one way or the other.
I mean, either "mdadm --verbose --examine --scan": all info,
or "mdadm --quiet --examine --scan": minimal info.
One of the two would be OK, I guess (not necessarly both).

> for the time being some akw magic can be used to parse 'mdadm --examine
> --scan' and make it suitable for inclusion in mdadm.conf

This is a possibility. It would be also OK to have a
script, delivered together with mdadm, doing this.
I can script myself, but a "standard solution" might
be better.

One question somehow related to this thread.

I would like to have my "fixed" RAIDs as devices with a
specific name.
That is, something like /dev/md/root and /dev/md/lvm (for
/dev/md0 and /dev/md1).
In this context, I would also like to have /dev/md0 and
/dev/md1 free to be used by other RAID.
Of course, I've no problem in using mdadm.conf for this,
but it seems that it is only possible something like
/dev/mdX or /dev/md/X.

Is this correct or there is some way to "personalize" the
created device name?

Thanks,

bye,

-- 

piergiorgio