From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] btrfs: Introduce new mount option to disable tree log replay
Date: Wed, 16 Dec 2015 11:10:48 +0000 (UTC) [thread overview]
Message-ID: <pan$ecec5$9f9ca76c$f1c4eebd$1e31c111@cox.net> (raw)
In-Reply-To: 5670C017.5010104@cn.fujitsu.com
Qu Wenruo posted on Wed, 16 Dec 2015 09:36:23 +0800 as excerpted:
> David Sterba wrote on 2015/12/14 18:32 +0100:
>> On Thu, Dec 10, 2015 at 10:34:06AM +0800, Qu Wenruo wrote:
>>> Introduce a new mount option "nologreplay" to co-operate with "ro"
>>> mount option to get real readonly mount, like "norecovery" in ext* and
>>> xfs.
>>>
>>> Since the new parse_options() need to check new flags at remount time,
>>> so add a new parameter for parse_options().
>>>
>>> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
>>> Reviewed-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
>>> Tested-by: Austin S. Hemmelgarn <ahferroin7@gmail.com>
>>
>> I've read the discussions around the change and from the user's POV I'd
>> suggest to add another mount option that would be just an alias for any
>> mount options that would implement the 'hard-ro' semantics.
>>
>> Say it's called 'nowr'. Now it would imply 'nologreplay', but may cover
>> more options in the future.
>>
>> mount -o ro,nowr /dev/sdx /mnt
>>
>> would work when switching kernels.
>>
>>
> That would be nice.
>
> I'd like to forward the idea/discussion to filesystem ml, not only btrfs
> maillist.
>
> Such behavior should better be coordinated between all(at least xfs and
> ext4 and btrfs) filesystems.
>
> One sad example is, we can't use 'norecovery' mount option to disable
> log replay in btrfs, as there is 'recovery' mount option already.
>
> So I hope we can have a unified mount option between mainline
> filesystems.
FWIW, I was just reading the mount manpage in connection with a reply for
a different thread, and noticed...
mount (8) (from util-linux 2.27.1) says noload and norecovery are the
same option, for ext3/4 at least. It refers to the xfs (5) manpage, from
xfsprogs, for xfs mount options, and that's not installed here, so I
can't confirm noload for it, but it's there for ext3/4.
And noload doesn't have the namespace collision problem norecovery does
on btrfs, so I'd strongly suggest using it, at least as an alias for
whatever other btrfs-specific name we might choose.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-12-16 11:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 2:34 [PATCH v3] btrfs: Introduce new mount option to disable tree log replay Qu Wenruo
2015-12-14 17:32 ` David Sterba
2015-12-14 17:50 ` Austin S. Hemmelgarn
2015-12-14 19:16 ` Christoph Anton Mitterer
2015-12-14 19:33 ` Austin S. Hemmelgarn
2015-12-14 19:44 ` Christoph Anton Mitterer
2015-12-14 20:20 ` Austin S. Hemmelgarn
2015-12-14 23:34 ` Christoph Anton Mitterer
2015-12-15 13:31 ` Austin S. Hemmelgarn
2015-12-16 13:53 ` David Sterba
2015-12-14 19:11 ` Christoph Anton Mitterer
2015-12-16 1:36 ` Qu Wenruo
2015-12-16 2:13 ` Christoph Anton Mitterer
2015-12-16 11:10 ` Duncan [this message]
2015-12-16 11:45 ` Christoph Anton Mitterer
2015-12-17 1:09 ` Duncan
2015-12-17 1:46 ` Christoph Anton Mitterer
2015-12-16 12:12 ` Austin S. Hemmelgarn
2015-12-16 12:34 ` Christoph Anton Mitterer
2015-12-16 12:57 ` Austin S. Hemmelgarn
2015-12-16 13:01 ` Christoph Anton Mitterer
2015-12-16 13:58 ` David Sterba
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='pan$ecec5$9f9ca76c$f1c4eebd$1e31c111@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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