linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems
Date: Fri, 15 Jan 2016 18:51:00 +0100	[thread overview]
Message-ID: <20160115175059.GH4227@suse.cz> (raw)
In-Reply-To: <56985046.1030306@cn.fujitsu.com>

On Fri, Jan 15, 2016 at 09:49:58AM +0800, Qu Wenruo wrote:
> David Sterba wrote on 2016/01/14 17:00 +0100:
> > On Tue, Jan 12, 2016 at 10:05:11AM +0800, Qu Wenruo wrote:
> >> '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 is changing during all these version changes.
> >
> > So we have some kind of consensus about the options, but I think you
> > need to split the patches further.
> 
> It's never a bad idea to split patches :)

My comment was motivated by the patch that introduced nologreplay and
norecovery in one go, although the functionality is logically separate
from the user's POV.

> > * the new option 'nologreplay'
> > * keep 'usebackuproot' as a new alias for 'recovery' (with the
> >    deprecation warning)
> > * new 'norecovery' that switches on 'nologreplay' and 'nousebackuproot'
> >    (ie. the desired "no writes")
> >
> > There is a case in remount, when we start with 'ro,nologreplay' then
> > remount with just 'ro', the log should be replayed. The other
> > combinations should be easy. I haven't looked at the patch if it's
> > implemented that way though.
> >
> >
> For that case, even remount with -o remount,ro the nologreplay mount 
> option won't be erased.
> That's why we added a lot of "noXXXX" mount option, or we can't disable 
> some feature by remount.

Yeah, I've realized that later that we need the 'logreplay' option to
achieve the readonly transition to the replayed state.

> And since I didn't add such "logreplay" mount option intentionally, so 
> there is no way to replay log unless umount the fs and mount it without 
> "nologreplay" again.
> 
> I'll update the patchset soon and hopes it can catch the rc1 merge window.

Yeah, I'd like to see it 4.5 as well, the topic has been discussed
enough and the implementation is simple.

  reply	other threads:[~2016-01-15 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  2:05 [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems Qu Wenruo
2016-01-12  2:05 ` [PATCH v5 1/2] btrfs: Introduce new mount option usebackuproot to replace recovery Qu Wenruo
2016-01-12  2:05 ` [PATCH v5 2/2] btrfs: Introduce new mount option to disable tree log replay Qu Wenruo
2016-01-14 16:00 ` [PATCH v5 0/2][PULL REQUEST] Unify 'norecovery' bahavior with other filesystems David Sterba
2016-01-15  1:49   ` Qu Wenruo
2016-01-15 17:51     ` David Sterba [this message]
2016-01-19  1:36   ` 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=20160115175059.GH4227@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.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;
as well as URLs for NNTP newsgroup(s).