From: Luca Berra <bluca@comedia.it>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm git pull] imsm fixes and general external metadata updates
Date: Tue, 24 Feb 2009 08:57:33 +0100 [thread overview]
Message-ID: <20090224075733.GE19209@maude.comedia.it> (raw)
In-Reply-To: <78a6226da1dee8c5b070b9ee30ee4705.squirrel@neil.brown.name>
On Tue, Feb 24, 2009 at 07:16:06AM +1100, NeilBrown wrote:
>On Tue, February 24, 2009 6:53 am, Doug Ledford wrote:
>> 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.
>
>This from fs/ext3/super.c
>
> if (EXT3_HAS_INCOMPAT_FEATURE(sb, EXT3_FEATURE_INCOMPAT_RECOVER)) {
> if (sb->s_flags & MS_RDONLY) {
> printk(KERN_INFO "EXT3-fs: INFO: recovery "
> "required on readonly filesystem.\n");
> if (really_read_only) {
> printk(KERN_ERR "EXT3-fs: write access "
> "unavailable, cannot proceed.\n");
> return -EROFS;
> }
> printk (KERN_INFO "EXT3-fs: write access will "
> "be enabled during recovery.\n");
> }
> }
>
>suggests that, unfortunately, you are.
>
am i misreading or the above is just a check not to
incur in further problems later?
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:[~2009-02-24 7:57 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
2009-02-23 20:16 ` NeilBrown
2009-02-24 7:57 ` Luca Berra [this message]
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=20090224075733.GE19209@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 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).