public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 0/3] Btrfs in-band de-duplication test cases
Date: Tue, 21 Mar 2017 15:48:37 +0800	[thread overview]
Message-ID: <20170321074837.GU14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <7756e826-f3ab-edf9-8581-63031c24b3f2@cn.fujitsu.com>

On Tue, Mar 21, 2017 at 03:36:54PM +0800, Qu Wenruo wrote:
> 
> 
> At 03/21/2017 03:23 PM, Eryu Guan wrote:
> > On Thu, Mar 16, 2017 at 09:50:24AM +0800, Qu Wenruo wrote:
> > > Btrfs in-band de-duplication test cases for in-memory backend, which covers
> > > the bugs exposed during the development.
> > 
> > Sorry, I'm having trouble enabling inband dedupe in tests, I always get
> > ioctl failure, $seqres.full shows:
> > 
> > btrfs-progs v4.10-5-g23d4fd5
> > See https://urldefense.proofpoint.com/v2/url?u=http-3A__btrfs.wiki.kernel.org&d=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=-yMrTV4jriXR7ieyzzjV-QgHBD0UDw8ixoR77aMeAHE&m=fSE-SZFHxYOtme73LUGhdAkjjKVeu59aewsxj3KYT8Q&s=wL4wtAJyaJ3YtkcV6849DAoedG_3c8E0ngquYDlE9ns&e=  for more information.
> > 
> > Label:              (null)
> > UUID:               3d2cedd0-64ae-4667-ba09-9c12e28ecadd
> > Node size:          16384
> > Sector size:        4096
> > Filesystem size:    15.00GiB
> > Block group profiles:
> >   Data:             single            8.00MiB
> >   Metadata:         DUP               1.00GiB
> >   System:           DUP               8.00MiB
> > SSD detected:       no
> > Incompat features:  extref, skinny-metadata
> > Number of devices:  1
> > Devices:
> >    ID        SIZE  PATH
> >     1    15.00GiB  /dev/mapper/systemvg-testlv2
> > 
> > # /usr/local/bin/btrfs dedupe enable -f -s inmemory -b 64K /scratch
> > ERROR: failed to (enable) inband deduplication: Inappropriate ioctl for device
> > ERROR: unsupported dedupe limit combination: nr: 0, mem: 0
> 
> What I forgot to mention is that, the inband dedupe feature is an
> experimental feature, so CONFIG_BTRFS_DEBUG is needed to use this feature.

OK, I'll rebuild with BTRFS_DEBUG and try again, thanks for the info!
But IMHO, giving out experimental message in dmesg seems sufficient,
like what XFS reflink feature does.

> 
> Sorry for the inconvenience.
> 
> I'll add also add the CONFIG_BTRFS_DEBUG check for /sys/fs/btrfs/feature/,
> so it won't export inband dedupe to users.

I'd suggest that adding a new require rule to check if inband dedupe is
supported by current kernel, by enabling inband dedupe and see the
result, so that we don't need to update the CONFIG_BTRFS_DEBUG check
when this feature is moved out of BTRFS_DEBUG.

Thanks,
Eryu
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=-yMrTV4jriXR7ieyzzjV-QgHBD0UDw8ixoR77aMeAHE&m=fSE-SZFHxYOtme73LUGhdAkjjKVeu59aewsxj3KYT8Q&s=EWR8R6A6ZhG1pWEZAhSGUJ2opiKV_e5FsB5X3ZMVxLE&e= 

      reply	other threads:[~2017-03-21  7:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16  1:50 [PATCH 0/3] Btrfs in-band de-duplication test cases Qu Wenruo
2017-03-16  1:50 ` [PATCH 1/3] fstests: btrfs: Add basic test for btrfs in-band de-duplication Qu Wenruo
2017-03-16  8:08   ` Eryu Guan
2017-03-16  8:33     ` Qu Wenruo
2017-03-16  1:50 ` [PATCH] fstests: generic: Test space allocation when there is only fragmented space Qu Wenruo
2017-03-16  1:50 ` [PATCH 2/3] fstests: btrfs: Add testcase for btrfs dedupe and metadata balance race test Qu Wenruo
2017-03-16  8:10   ` Eryu Guan
2017-03-16  1:50 ` [PATCH 3/3] fstests: btrfs: Test inband dedupe with data balance Qu Wenruo
2017-03-21  7:23 ` [PATCH 0/3] Btrfs in-band de-duplication test cases Eryu Guan
2017-03-21  7:36   ` Qu Wenruo
2017-03-21  7:48     ` Eryu Guan [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=20170321074837.GU14226@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --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