From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH V6 2/3] btrfs: Introduce new mount option to disable tree log replay
Date: Tue, 19 Jan 2016 10:12:58 +0800 [thread overview]
Message-ID: <569D9BAA.3090106@cn.fujitsu.com> (raw)
In-Reply-To: <1453168792.6445.2.camel@scientia.net>
Christoph Anton Mitterer wrote on 2016/01/19 02:59 +0100:
> On Tue, 2016-01-19 at 09:49 +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.
>
> What happened to the nice plans to get a proper dedicated mount option
> for hard ro mounts, that will work even as btrfs changes and would
> require further options to get that behaviour?
>
> Chris.
>
Sorry, I'm convinced by the fsdevel guys, and know I also believe we
don't need to make things too complicated.
Just norecovery should be good enough.
Further hard ro would need use blockdev to set device to RO.
Thanks,
Qu
next prev parent reply other threads:[~2016-01-19 2:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 1:49 [PATCH V6 0/3][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems Qu Wenruo
2016-01-19 1:49 ` [PATCH V6 1/3] btrfs: Introduce new mount option usebackuproot to replace recovery Qu Wenruo
2016-01-19 2:00 ` Christoph Anton Mitterer
2016-01-19 2:13 ` Qu Wenruo
2016-01-19 1:49 ` [PATCH V6 2/3] btrfs: Introduce new mount option to disable tree log replay Qu Wenruo
2016-01-19 1:59 ` Christoph Anton Mitterer
2016-01-19 2:12 ` Qu Wenruo [this message]
2016-01-19 1:49 ` [PATCH V6 3/3] btrfs: Introduce new mount option alias for nologreplay Qu Wenruo
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=569D9BAA.3090106@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=calestyo@scientia.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;
as well as URLs for NNTP newsgroup(s).