From: Luca Berra <bluca@comedia.it>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Minor mdadm fixes
Date: Fri, 19 Mar 2010 08:01:53 +0100 [thread overview]
Message-ID: <20100319070153.GA12455@maude.comedia.it> (raw)
In-Reply-To: <4BA2DDB2.2040508@redhat.com>
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 ?
it is messy enough as it is, let's keep assuming /dev/md contains only
array device files.
besides that you will discover that the only way to make mdmon work is
setting VAR_RUN and ALT_RUN to the same value, something we can
guarantee to be writable even in the direst situation, and i'd keep
/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? 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)
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2010-03-19 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 2:13 Minor mdadm fixes Doug Ledford
2010-03-19 7:01 ` Luca Berra [this message]
2010-03-23 19:20 ` Doug Ledford
2010-03-23 20:28 ` Luca Berra
2010-03-24 0:27 ` Neil Brown
2010-03-24 17:48 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2010-01-11 20:38 Doug Ledford
2010-01-12 0:49 ` Mr. James W. Laferriere
2010-01-12 3:10 ` Andre Noll
2010-01-12 3:36 ` Doug Ledford
2010-01-12 4:39 ` Andre Noll
2010-01-12 4:46 ` Doug Ledford
2010-01-12 5:21 ` Andre Noll
2010-01-18 22:05 ` Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100319070153.GA12455@maude.comedia.it \
--to=bluca@comedia.it \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.