From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Cc: initramfs@vger.kernel.org
Subject: Re: [[Patch mdadm] 2/5] Move the files mdmon opens into /dev/ to support handoff after pivotroot
Date: Tue, 2 Feb 2010 08:17:26 +0100 [thread overview]
Message-ID: <20100202071726.GB24147@maude.comedia.it> (raw)
In-Reply-To: <4877c76c1002012008u2e32d6a4y9b4fec721dfe8435@mail.gmail.com>
Ccing intramfs since it could be of interest
background:
Doug's patch moves mdmon pid file and socket from /var/run to /dev
to preserve them after pivot-root
Rationale is mdmon gets started in initramfs when imsm or ddf arrays are
activated.
Neil does not like the proposed solution
On Mon, Feb 01, 2010 at 08:08:54PM -0800, Michael Evans wrote:
>On Mon, Feb 1, 2010 at 2:42 PM, Bill Davidsen <davidsen@tmr.com> wrote:
>> Doug Ledford wrote:
>>>
>>> On 02/01/2010 03:32 PM, Bill Davidsen wrote:
>>>
>>>>
>>>> Doug Ledford wrote:
>>>>
>>>>>
>>>>> On 01/18/2010 05:09 PM, Neil Brown wrote:
>>>>>
>>>>>>
>>>>>> I understand there is a problem here, but I don't like this approach
>>>>>> to a
>>>>>> solution. I'll give it more though when I get home from LCA2010 and
>>>>>> see
>>>>>> what I can come up with.
>>>>>>
>>>>>
>>>>> Feel free to come up with something different. But, if your solution
>>>>> involves maintaining an additional read/write mount area in deference to
>>>>> a long dead unix tradition, I'm just going to shake my head and patch
>>>>> your solution away to something sane.
>>>>>
>>>>>
>>>>
>>>> I don't understand you argument here. Not the one where you say you're
>>>> going to ignore Neil and do what you want because you can, I understand
>>>> that, but the "additional read/write mount area" part, isn't /var/run
>>>> r/w on all systems now? Could you clarify why this is "additional" here?
>>>>
>>>>
>>>
>>> It's not necessarily read/write in the initrd time frame, and putting
>>> the mdadm files there means it would have to be. We didn't make these
>>> changes because we wanted to, we made them because using mdadm raid
>>> arrays for the root filesystem combined with incremental assembly or
>>> with imsm raid devices was broken otherwise.
>>>
>>>
>>
>> Do understand that my disquiet related to this isn't because you put a
>> non-device in /dev, it's that you
>> didn't put a process PID in /var/run. And frankly, once you let (force) one
>> group of threads to be somewhere
>> else, other services will want their PIDs some other place, and anyone
>> maintaining an application
>> which presents information on what's running will need to know where that
>> information.
>>
>> In other words, it's not where you put it, it's where you *didn't* put it,
>> that seems to be an
>> invitation to put stuff just anywhere. Neil argues that they are not
>> devices, I argue that
>> they are PIDs. It's not as though it were a huge effort to move it after
>> pivot root, it's a little code
>> or script and in space which will be released.
>>
>> --
>> Bill Davidsen <davidsen@tmr.com>
>> "We can't solve today's problems by using the same thinking we
>> used in creating them." - Einstein
>>
>> --
>> 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
>>
>
>Thank you for stating your concern; I think knowing that a very
>plausible solution is obvious.
>
># at initrd/initramfs creation time
>ln -s /dev/.run /var/run
>
>#initrd/initramfs script
>mkdir /dev/.run
>
>The usual area becomes a symlink to a memory disk .Most systems have
>ample memory to support a few extra tiny files there. Cleanup on
>reboot is automatic. Any systems that are memory constrained probably
>already either have a drive they could swap this data out to, or would
>rather save the writes from reaching flash media anyway.
this could be interesting, but then you have to move things back to
/var/run after pivot root, and we cannot move a socket.
still if it would suit both parties we could
- keep the mdmon pid file in /var/run and use initramfs magik to preserve
those pid files, this could become a standard solution when the next
daemon arrives that needs to start from initramfs.
- put the socket in /dev/md, and i defy anyone to say sockets do not belong
in /dev, bringing forth the syslog daemon as a witness.
Regards,
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
--
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
next parent reply other threads:[~2010-02-02 7:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1263242294-5353-1-git-send-email-dledford@redhat.com>
[not found] ` <1263242294-5353-3-git-send-email-dledford@redhat.com>
[not found] ` <20100119110930.107ca42e@notabene>
[not found] ` <4B55F138.7060008@redhat.com>
[not found] ` <4B673A5D.2010901@tmr.com>
[not found] ` <4B674860.7080604@redhat.com>
[not found] ` <4B6758C7.9060301@tmr.com>
[not found] ` <4877c76c1002012008u2e32d6a4y9b4fec721dfe8435@mail.gmail.com>
2010-02-02 7:17 ` Luca Berra [this message]
2010-02-04 6:40 ` [[Patch mdadm] 2/5] Move the files mdmon opens into /dev/ to support handoff after pivotroot Neil Brown
2010-02-04 18:45 ` Doug Ledford
[not found] ` <4B6B15B3.8030205-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-02-04 23:04 ` Dan Williams
[not found] ` <e9c3a7c21002041504w17565653m5a8b8cd90543cf1e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-05 0:21 ` Bill Davidsen
2010-02-06 17:51 ` Doug Ledford
[not found] ` <4B6DAC06.6060909-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-02-06 21:07 ` Dan Williams
[not found] ` <e9c3a7c21002061307le6f5d56ked4fa3711bdd2367-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-06 21:46 ` martin f krafft
2010-02-06 22:06 ` Michael Evans
2010-02-08 15:32 ` Doug Ledford
2010-02-08 21:38 ` Neil Brown
2010-02-09 0:20 ` Michael Evans
[not found] ` <20100209083838.6568cac0-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2010-02-09 2:19 ` martin f krafft
[not found] ` <20100209021949.GB11780-0owbi4v4jRjYceiJAzDLgeTW4wlIGRCZ@public.gmane.org>
2010-02-09 20:34 ` Doug Ledford
[not found] ` <4B71C6CA.3010407-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-02-10 0:58 ` Mr. James W. Laferriere
[not found] ` <alpine.LNX.2.01.1002091553580.10004-pIN9qAC4yfKseEBmXaVrNB5FPEiCeG3sAL8bYrjMMd8@public.gmane.org>
2010-02-10 1:33 ` Neil Brown
2010-02-10 9:46 ` Harald Hoyer
[not found] ` <20100210123321.324e5de6-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2010-02-10 15:49 ` Dan Williams
2010-02-10 16:06 ` Michael Evans
[not found] ` <4877c76c1002100806w66e504deg767f6ecc8cc7fa8a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-11 2:30 ` Doug Ledford
2010-02-09 20:30 ` Doug Ledford
2010-02-08 4:23 ` Neil Brown
2010-02-07 22:13 ` Hans de Goede
2010-02-07 23:06 ` Neil Brown
2010-02-08 3:45 ` Neil Brown
2010-02-08 16:56 ` Bill Nottingham
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=20100202071726.GB24147@maude.comedia.it \
--to=bluca@comedia.it \
--cc=initramfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox