linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext3: make "norecovery" an alias for "noload"
Date: Thu, 19 Nov 2009 09:57:44 -0600	[thread overview]
Message-ID: <4B056AF8.3010604@redhat.com> (raw)
In-Reply-To: <20091119151233.GE24836@duck.suse.cz>

Jan Kara wrote:
> On Mon 16-11-09 16:50:49, Eric Sandeen wrote:
>> Users on the list recently complained about differences across
>> filesystems w.r.t. how to mount without a journal replay.
>>
>> In the discussion it was noted that xfs's "norecovery" option is
>> perhaps more descriptively accurate than "noload," so let's make
>> that an alias for ext3.
>>
>> Also show this status in /proc/mounts
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>   OK, provided ext4 will have the same change, I'm fine with the patch.
> So how is it with ext4?

I did send the same patch for ext4

"[PATCH 2/2] ext4: make "norecovery" an alias for "noload""

Thanks,
-Eric

> 									Honza
>> ---
>>
>> diff --git a/Documentation/filesystems/ext3.txt b/Documentation/filesystems/ext3.txt
>> index 05d5cf1..8b8d973 100644
>> --- a/Documentation/filesystems/ext3.txt
>> +++ b/Documentation/filesystems/ext3.txt
>> @@ -33,7 +33,7 @@ journal_dev=devnum	When the external journal device's major/minor numbers
>> 			in devnum.
>>
>> noload			Don't load the journal on mounting. Note that this forces
>> -			mount of inconsistent filesystem, which can lead to
>> +norecovery		mount of inconsistent filesystem, which can lead to
>> 			various problems.
>>
>> data=journal		All data are committed into the journal prior to being
>> diff --git a/fs/ext3/super.c b/fs/ext3/super.c
>> index 427496c..c14fb95 100644
>> --- a/fs/ext3/super.c
>> +++ b/fs/ext3/super.c
>> @@ -636,6 +636,9 @@ static int ext3_show_options(struct seq_file *seq, struct vfsmount *vfs)
>> 	if (test_opt(sb, DATA_ERR_ABORT))
>> 		seq_puts(seq, ",data_err=abort");
>>
>> +	if (test_opt(sb, NOLOAD))
>> +		seq_puts(seq, ",norecovery");
>> +
>> 	ext3_show_quota_options(seq, sb);
>>
>> 	return 0;
>> @@ -818,6 +821,7 @@ static const match_table_t tokens = {
>> 	{Opt_reservation, "reservation"},
>> 	{Opt_noreservation, "noreservation"},
>> 	{Opt_noload, "noload"},
>> +	{Opt_noload, "norecovery"},
>> 	{Opt_nobh, "nobh"},
>> 	{Opt_bh, "bh"},
>> 	{Opt_commit, "commit=%u"},
>>


  reply	other threads:[~2009-11-19 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 22:50 [PATCH] ext3: make "norecovery" an alias for "noload" Eric Sandeen
2009-11-19 15:12 ` Jan Kara
2009-11-19 15:57   ` Eric Sandeen [this message]
2009-11-19 16:10     ` Jan Kara
2009-11-19 19:33   ` tytso
2009-11-20 15:41     ` Eric Sandeen

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=4B056AF8.3010604@redhat.com \
    --to=sandeen@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@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).