public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>,
	Dave Chinner <david@fromorbit.com>,
	xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] mkfs: enable reflink and rmap by default
Date: Fri, 3 May 2019 14:49:13 -0700	[thread overview]
Message-ID: <20190503214913.GR5207@magnolia> (raw)
In-Reply-To: <b406bac9-1899-1714-a14f-472fb4bbaffd@sandeen.net>

On Fri, May 03, 2019 at 10:55:05AM -0500, Eric Sandeen wrote:
> On 5/2/19 7:57 PM, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > Enable reflink and reverse mapping by default.
> 
> Soooo until now, I thought I had understood that rmap was unlikely
> to be default ever, due to performance impacts.  Is this no longer the case?

No, it's still the case.

> Of course I can't find any emails or IRC logs to indicate I didn't
> just dream this up...
> 
> Also, at this point, remind me again what uses rmap and why it should
> be enabled now?

TBH it's most useful for enhancing xfs_scrub's powers, so there's no
reason to enable it by default until at least 5.2 when we finally land
the last of the scrubbers.  Probably.  One could make a solid argument
that we ought to wait until the scrub/health code has been stable for
~6mo before even thinking about rmap by default.

Anyway I'll break this into separate pieces and resend the reflink part
for 5.1.

--D

> 
> -Eric
> 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> >  mkfs/xfs_mkfs.c |    8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> > index 0862621a..3874f7dd 100644
> > --- a/mkfs/xfs_mkfs.c
> > +++ b/mkfs/xfs_mkfs.c
> > @@ -2021,14 +2021,14 @@ _("sparse inodes not supported without CRC support\n"));
> >  		}
> >  		cli->sb_feat.spinodes = false;
> >  
> > -		if (cli->sb_feat.rmapbt) {
> > +		if (cli->sb_feat.rmapbt && cli_opt_set(&mopts, M_RMAPBT)) {
> >  			fprintf(stderr,
> >  _("rmapbt not supported without CRC support\n"));
> >  			usage();
> >  		}
> >  		cli->sb_feat.rmapbt = false;
> >  
> > -		if (cli->sb_feat.reflink) {
> > +		if (cli->sb_feat.reflink && cli_opt_set(&mopts, M_REFLINK)) {
> >  			fprintf(stderr,
> >  _("reflink not supported without CRC support\n"));
> >  			usage();
> > @@ -3934,8 +3934,8 @@ main(
> >  			.dirftype = true,
> >  			.finobt = true,
> >  			.spinodes = true,
> > -			.rmapbt = false,
> > -			.reflink = false,
> > +			.rmapbt = true,
> > +			.reflink = true,
> >  			.parent_pointers = false,
> >  			.nodalign = false,
> >  			.nortalign = false,
> > 

      reply	other threads:[~2019-05-03 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03  0:57 [PATCH] mkfs: enable reflink and rmap by default Darrick J. Wong
2019-05-03 15:55 ` Eric Sandeen
2019-05-03 21:49   ` Darrick J. Wong [this message]

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=20190503214913.GR5207@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sandeen@sandeen.net \
    /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