linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH V7 0/3][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
Date: Tue, 19 Jan 2016 10:23:01 +0800	[thread overview]
Message-ID: <1453170184-22869-1-git-send-email-quwenruo@cn.fujitsu.com> (raw)

'Norecovery' mount option is almost a standard for all other
filesystems, including f2fs, ext4, gfs2, nilfs2, and xfs.
And since current 'recovery' mount option for btrfs is too generic, it's
better to change btrfs 'recovery' to 'usebackuproot' and then we can
safely add 'norecovery' and 'nologreplay' mount option for btrfs.

The patch itself is not huge and already tested by others since v2.
Only mount option name and patch slipting is changing during all
these version changes.

Qu Wenruo (3):
  btrfs: Introduce new mount option usebackuproot to replace recovery
  btrfs: Introduce new mount option to disable tree log replay
  btrfs: Introduce new mount option alias for nologreplay

 Documentation/filesystems/btrfs.txt | 17 +++++++++++---
 fs/btrfs/ctree.h                    |  6 +++--
 fs/btrfs/disk-io.c                  | 15 ++++++++----
 fs/btrfs/super.c                    | 47 ++++++++++++++++++++++++++++++-------
 4 files changed, 67 insertions(+), 18 deletions(-)

-- 
2.7.0




             reply	other threads:[~2016-01-19  2:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  2:23 Qu Wenruo [this message]
2016-01-19  2:23 ` [PATCH V7 1/3] btrfs: Introduce new mount option usebackuproot to replace recovery Qu Wenruo
2016-02-12 13:05   ` David Sterba
2016-01-19  2:23 ` [PATCH V7 2/3] btrfs: Introduce new mount option to disable tree log replay Qu Wenruo
2016-01-19  2:23 ` [PATCH V7 3/3] btrfs: Introduce new mount option alias for nologreplay Qu Wenruo
2016-01-29  3:17 ` [PATCH V7 0/3][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems Qu Wenruo
2016-02-01 23:16   ` David Sterba
2016-02-12 14:18   ` David Sterba
2016-02-14  2:05     ` 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=1453170184-22869-1-git-send-email-quwenruo@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --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).