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:23:40 +0800 [thread overview]
Message-ID: <20170321072340.GT14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170316015028.20020-1-quwenruo@cn.fujitsu.com>
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=QW8j5ytjvhSULN9SgVewhinVZVh9U-etu9FpCxFlsCc&s=N3fHeukNWyZ1Av8wPL6uQRaIzk0Y6Z90W-7loCAj4J8&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
failed: '/usr/local/bin/btrfs dedupe enable -f -s inmemory -b 64K /scratch'
I have no special MKFS_OPTIONS or MOUNT_OPTIONS specified, all defaults.
kernel is built from your test tree. Did I miss anything?
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=QW8j5ytjvhSULN9SgVewhinVZVh9U-etu9FpCxFlsCc&s=eaJ-tn7MdocpEA2Dssf3q1tiBAMCKm3MbKiI4S_bkL0&e=
next prev parent reply other threads:[~2017-03-21 7:23 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 ` Eryu Guan [this message]
2017-03-21 7:36 ` [PATCH 0/3] Btrfs in-band de-duplication test cases Qu Wenruo
2017-03-21 7:48 ` Eryu Guan
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=20170321072340.GT14226@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