Hello Neil ,
On Fri, 15 Feb 2002, Neil Brown wrote:
> On Thursday February 14, babydr@baby-dragons.com wrote:
> > Hello All , That subject reminded me that I have seen some notes
> > in the 0.5 TODO file that say DONE & seem to be related to a
> > config file for mdctl . The only example of a config file I found
> > was in 0.4.2 and is two lines long . And did not show any of the
> > related items from the 0.5 TODO file of course . What I have
> > below is from the config.c file . Is there further document(s)
> > or examples that describe the config file in further detail ?
> > Tia , JimL
> I guess I should improve the doco and do another release...
Thank you for responding . All I want to do is attempt to
document the possible syntax(s) of the file . Then I'd like
to submit a patch to allow mdctl to create a mdctl.conf from
an existing array .
> > 1 ) Keywords are :
> > DEVICE
> > ARRAY
> Yep.
> > 2 ) DEVice has two styles
> > DEV /dev/sda* /dev/hd*
> > DEV /dev/sd[b-f]*
> these are both the same style. You just list all devices that should
> scanned, and you can use "glob"-style wild cards (aka shell filename
> expansion style).
What is the "glob"-style based on ? Bash/Regex/...
> > 3 ) ARRay Must contain a /dev/md* & May contain these options .
> > ARR /dev/md0 [uuid=whatever] [name=something]
> name=something doesn't work (yet) as superblocks do not contain a
> name.
Ok , What is lacking (other than time;-) to accomplish this
task ?
> The ways to identify a devices are:
> uuid=whatever
> super-minor=number
> devices=/dev/hda1,/dev/hdb1
> The first will assemble from any devices that were found with a RAID
> superblock with the given uuid.
I take it (from below) that this is only if mdctl (at present)
has written those UUID's ? Iirc , UUID's are not attached to a
disk but to a file system . Or is this after a file system has
been created on the array ?
>< UUID can be found with "mdctl --examine"
??? , On a non-mdctl built 0.90.0 array ie: partitions 0xfd .
# mdctl --examine /dev/md0
mdctl: No super block found on /dev/md0 (Expected magic a92b4efc, got 00000000)
But :
# mdctl --detail /dev/md0
...snip...
UUID : b285b144:ae0b561b:b5b55686:ed216a4c
What am I missing here ?
> The second will select superblocks based on minor number. If you
> create an array as /dev/md3, then the minor number in the superblock
> will be 3.
This one I am (pretty) sure that mdctl has to write this one .
Or do all of the present tools do this as well ? I don't have
an idle md array to play with to find out .
> The third will use the listed devices. This is not reliably for scsi
> as device names can change, but it is ok for ide.
Man do I know that one :-} . Tia , JimL
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
