On 03/19/2010 03:01 AM, Luca Berra wrote:
> On Thu, Mar 18, 2010 at 10:13:06PM -0400, Doug Ledford wrote:
>> Second: mdadm-3.1.2-mapfile.patch
>> Problem: Neil's support for putting the mdadm map file wherever you need
>> it is nice, but one place in particular needs a special case.
>> Specifically, mdadm already creates /dev/md if needed to store symlinks,
>> or in the case of mdmon needing to create pid/sock files (if ALT_RUN is
> why on earth do you want to set ALT_RUN=/dev/md ?
Because on Fedora /lib/init/rw doesn't exist, and neither does any other
early rw area other than /dev, and it's too late to create a new one, so
I need to use someplace in /dev. However, I agree with Neil that if you
are hiding things under . names then you are admitting something isn't
right. So, I'm perfectly happy putting the map file in /dev/md as I
think it has a perfect right to exist there.
> it is messy enough as it is, let's keep assuming /dev/md contains only
> array device files.
I don't know how many arrays you have on your system, but I would hardly
call /dev/md messy.
> besides that you will discover that the only way to make mdmon work is
> setting VAR_RUN and ALT_RUN to the same value,
[ citation needed ]
> something we can
> guarantee to be writable even in the direst situation, and i'd keep
> /dev/.mdadm
There is no guarantee /dev/.mdadm exists on a clean install, where as I
have made sure that all possible places that might need /dev/md will
create it if it doesn't exist. Hence, the direst of situations is
handled better with /dev/md than with /dev/.mdadm
>> Fourth: mdadm-3.1.2-mapname.patch
>> Feature: If we are able to easily select the location of the mapfile via
>> the use of ALT_RUN at compile time, it makes sense to also be able to
> this "hunt the mapfile" thing is already ugly as it is, why do we need
> an ALT_MAPNAME?
Because /dev/md/map is too easy a name to conflict with a legitimate md
array device name, and that's what it defaults to if you set ALT_RUN to
/dev/md.
> if there was any value (except for allowing to set
> ALT_RUN to /dev/md) to having the mapfile named differently, just force
> it to be called mdadm.map everywere (or incremental.map so the name
> reflects the need for the file existance)
Except I set it to md-device-map. Aside from not conflicting with md
device names, the map file name is mostly irrelevant except to indicate
to people perusing the directory what the file is for as nothing uses it
besides mdadm and mdadm will gladly use it with whatever name you call
it as it both creates and uses the file from the same compile time
configuration setting.
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
Attachment:
signature.asc
Description: OpenPGP digital signature
