From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] btrfs: Introduce new mount option to disable tree log replay
Date: Wed, 16 Dec 2015 12:45:00 +0100 [thread overview]
Message-ID: <1450266300.6259.2.camel@scientia.net> (raw)
In-Reply-To: <pan$ecec5$9f9ca76c$f1c4eebd$1e31c111@cox.net>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
On Wed, 2015-12-16 at 11:10 +0000, Duncan wrote:
> 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.
but noload is, AFAIU, not what's desired here, is it?
Per manpage it's "Don't load the journal on mounting",... not only
wouldn't that fit for btrfs, it's also not what's really desired, i.e.
an option that implies everything necessary to not modify the device.
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-12-16 11:45 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
2015-12-16 11:45 ` Christoph Anton Mitterer [this message]
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=1450266300.6259.2.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=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