From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Eric Sandeen <sandeen@redhat.com>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Introduce new mount option to disable tree log replay
Date: Tue, 08 Dec 2015 01:00:43 +0100 [thread overview]
Message-ID: <1449532843.6881.20.camel@scientia.net> (raw)
In-Reply-To: <566610FA.1080408@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Mon, 2015-12-07 at 17:06 -0600, Eric Sandeen wrote:
> Yeah, I don't know that this is true. It hasn't been true for over a
> decade (2?), with the most widely-used filesystem in linux history,
> i.e.
> ext3.
Based on what? I'd now many sysadmins who don't expect that e.g. the
journal is replayed when ext* is mounted ro.
> So if btrfs wants to go on this re-education crusade, more power
> to you, but I don't know that it's really a fight worth fighting. ;)
I don't think there's a bight fight necessary, is it?
Just properly document all options and not only from the developers or
expert-users PoV.
Using blockdev --setro is of course an alternative to a dedicated
"hard-ro" option (or something similar that goes by a better name),...
OTOH I don't think that having such an option would cause big problems
or "religion wars" ;)
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-12-08 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 6:06 [PATCH] btrfs: Introduce new mount option to disable tree log replay Qu Wenruo
2015-12-07 15:38 ` Chandan Rajendra
2015-12-07 23:51 ` Qu Wenruo
2015-12-07 16:27 ` Eric Sandeen
2015-12-07 16:52 ` Chandan Rajendra
2015-12-07 17:29 ` Eric Sandeen
2015-12-07 20:54 ` Christoph Anton Mitterer
2015-12-07 23:06 ` Eric Sandeen
2015-12-08 0:00 ` Christoph Anton Mitterer [this message]
2015-12-08 12:15 ` Austin S Hemmelgarn
2015-12-08 19:20 ` Christoph Anton Mitterer
2015-12-08 20:29 ` Austin S Hemmelgarn
2015-12-07 16:36 ` Austin S Hemmelgarn
2015-12-08 6:08 ` Qu Wenruo
2015-12-08 12:16 ` Austin S Hemmelgarn
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=1449532843.6881.20.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=chandan@linux.vnet.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.