From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 1/2] btrfs: Introduce new mount option backuproot to replace recovery
Date: Tue, 22 Dec 2015 07:44:22 -0500 [thread overview]
Message-ID: <567945A6.2000800@gmail.com> (raw)
In-Reply-To: <1450750596-14627-1-git-send-email-quwenruo@cn.fujitsu.com>
On 2015-12-21 21:16, Qu Wenruo wrote:
> Current "recovery" mount option will only try to use backup root.
> However the word "recovery" is too generic and may be confusing for some
> users.
>
> Here introduce a new and more specific mount option, "backuproot" to
> replace "recovery" mount option.
> "Recovery" will be kept for compatibility reason, but will be
> deprecated.
>
> Also, since "backuproot" will only affect mount behavior and after
> open_ctree() it has nothing to do with the filesystem, so clear the flag
> after mount succeeded.
>
> This provides the basis for later unified "norecovery" mount option.
>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> ---
> v4:
> Newly introduced to avoid confusion with later 'norecovery' patch.
> ---
I ran my usual tests overnight on this part, and nothing broke, so you
can add
Tested-by: Austin S. Hemmelgarn
here as well.
next prev parent reply other threads:[~2015-12-22 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 2:16 [PATCH v4 1/2] btrfs: Introduce new mount option backuproot to replace recovery Qu Wenruo
2015-12-22 2:16 ` [PATCH v4 2/2] btrfs: Introduce new mount option to disable tree log replay Qu Wenruo
2015-12-22 12:30 ` [PATCH v4 1/2] btrfs: Introduce new mount option backuproot to replace recovery Holger Hoffstätte
2015-12-22 14:21 ` Qu Wenruo
2015-12-22 16:55 ` Austin S. Hemmelgarn
2015-12-22 12:44 ` Austin S. Hemmelgarn [this message]
2015-12-22 21:35 ` Christoph Anton Mitterer
2015-12-23 5:09 ` 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=567945A6.2000800@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox