From: Doug Ledford <dledford@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm git pull] imsm fixes and general external metadata updates
Date: Mon, 23 Feb 2009 14:53:52 -0500 [thread overview]
Message-ID: <1235418832.751.385.camel@firewall.xsintricity.com> (raw)
In-Reply-To: <e9c3a7c20902231058x4196e688xa9091c72e31b1c4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
On Mon, 2009-02-23 at 11:58 -0700, Dan Williams wrote:
> On Mon, Feb 23, 2009 at 8:54 AM, Doug Ledford <dledford@redhat.com> wrote:
> > On Mon, 2009-02-02 at 10:46 +1100, Neil Brown wrote:
> >> We really need a man page for mdmon don't we. Then this sort of text
> >> could be placed there for safely.
> >
> > Yes, a man page is definitely needed.
>
> I have one brewing, I'll include it in an upcoming pull request.
>
> > I have no intention of putting
> > mdmon in the initramfs. The only arrays that should be started during
> > initramfs operation are / and possibly /boot. Both of those are started
> > readonly. It isn't until later in the boot process (in rc.sysinit on
> > Fedora/RHEL) that we remount the / device rw. It's my intention to
> > modify our rc.sysinit so that before the root device goes rw, we start
> > the necessary mdmon instances. This should be sufficient to keep the
> > container metadata state consistent with reality and avoids having to
> > add mdmon to the initramfs. However, that means I need to know how to
> > invoke mdmon when mdadm isn't starting it for me.
>
> Did you happen to catch the discussion on the initramfs mailing list
> [1]? It would be nice to not need mdmon in the initramfs. However, I
> have found it needs to be there because even read-only mounted
> filesystems require write access to the underlying block device to
> recover the journal.
>
> --
> Dan
>
> [1] http://thread.gmane.org/gmane.linux.kernel.initramfs/65/
Is XFS the only one that does the journal recovery on initial mount
read-only during the initfs step, or do other journaled fses do the same
thing? I didn't think ext3 recovered the journal until you switch to a
read-write mount, but I guess I could be wrong.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-23 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 22:20 [mdadm git pull] imsm fixes and general external metadata updates Dan Williams
2009-01-23 22:51 ` Dan Williams
2009-02-01 23:46 ` Neil Brown
2009-02-23 15:54 ` Doug Ledford
2009-02-23 18:58 ` Dan Williams
2009-02-23 19:53 ` Doug Ledford [this message]
2009-02-23 20:16 ` NeilBrown
2009-02-24 7:57 ` Luca Berra
2009-02-24 23:33 ` When read-only isn't read-only (was Re: [mdadm git pull] imsm fixes and general external metadata updates) John Robinson
2009-02-24 23:45 ` Greg Freemyer
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=1235418832.751.385.camel@firewall.xsintricity.com \
--to=dledford@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).