From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Mark Fasheh <mark@fasheh.com>,
dsterba@suse.cz, James Pharaoh <james@wellbehavedsoftware.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Announcing btrfs-dedupe
Date: Mon, 7 Nov 2016 18:17:23 -0800 [thread overview]
Message-ID: <20161108021722.GA16801@birch.djwong.org> (raw)
In-Reply-To: <20161107205409.GA20325@angband.pl>
On Mon, Nov 07, 2016 at 09:54:09PM +0100, Adam Borowski wrote:
> On Mon, Nov 07, 2016 at 09:48:41AM -0800, Mark Fasheh wrote:
> > also on XFS with the dedupe ioctl (I believe this should be out with
> > Linux-4.9).
>
> It's already there in 4.9-rc1, although you need a special version of
> xfsprogs (possibly already released, I didn't check). It's an experimental
> feature that needs to be enabled with "-m reflink=1".
The code will be available in xfsprogs 4.9, due out after Linux 4.9.
You'll still have to pass '-m reflink=1' to enable reflink until we
declare the feature stable, however.
> Despite that experimental status, I'd strongly recommend James to test his
> tool on xfs as well, as it's the second major implementation of this API[1].
Agreed. :)
> Mark has already included XFS in documentation of duperemove, all that looks
> amiss is btrfs-extent-same having an obsolete name. But then, I never did
> any non-superficial tests on XFS, beyond "seems to work".
/me wonders if ocfs2 will ever catch up to the reflink/dedupe party. ;)
--Darrick
>
>
> Meow!
>
> [1]. For some reasons zfs-on-linux guys didn't implement this yet, despite
> it being an obvious thing on ZFS.
> --
> A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
> raspberries, 0.4kg sugar; put into a big jar for 1 month. Filter out and
> throw away the fruits (can dump them into a cake, etc), let the drink age
> at least 3-6 months.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-08 2:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 13:30 Announcing btrfs-dedupe James Pharaoh
2016-11-07 14:02 ` David Sterba
2016-11-07 17:48 ` Mark Fasheh
2016-11-07 20:54 ` Adam Borowski
2016-11-08 2:17 ` Darrick J. Wong [this message]
2016-11-08 18:59 ` Mark Fasheh
2016-11-08 19:47 ` Darrick J. Wong
2016-11-09 15:02 ` David Sterba
2016-11-08 2:40 ` Christoph Anton Mitterer
2016-11-08 6:11 ` James Pharaoh
2016-11-08 13:26 ` Austin S. Hemmelgarn
2016-11-08 16:57 ` Darrick J. Wong
2016-11-08 17:04 ` Austin S. Hemmelgarn
2016-11-08 18:49 ` Mark Fasheh
2016-11-07 17:59 ` Mark Fasheh
2016-11-07 18:49 ` James Pharaoh
2016-11-07 18:53 ` James Pharaoh
2016-11-14 18:07 ` Zygo Blaxell
2016-11-14 18:22 ` James Pharaoh
2016-11-14 18:39 ` Austin S. Hemmelgarn
2016-11-14 19:51 ` Zygo Blaxell
2016-11-14 19:56 ` Austin S. Hemmelgarn
2016-11-14 21:10 ` Zygo Blaxell
2016-11-15 12:26 ` Austin S. Hemmelgarn
2016-11-15 17:52 ` Zygo Blaxell
2016-11-16 22:24 ` Niccolò Belli
2016-11-17 3:01 ` Zygo Blaxell
2016-11-18 10:36 ` Niccolò Belli
2016-11-14 20:07 ` James Pharaoh
2016-11-14 21:22 ` Zygo Blaxell
2016-11-14 18:43 ` Zygo Blaxell
2016-11-08 11:06 ` Niccolò Belli
2016-11-08 11:38 ` James Pharaoh
2016-11-08 16:57 ` Niccolò Belli
2016-11-08 16:58 ` James Pharaoh
2016-11-08 17:08 ` Niccolò Belli
2016-11-14 18:27 ` Zygo Blaxell
2016-11-08 22:36 ` Saint Germain
2016-11-09 11:24 ` Niccolò Belli
2016-11-09 12:47 ` Saint Germain
2016-11-13 12:45 ` James Pharaoh
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=20161108021722.GA16801@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=dsterba@suse.cz \
--cc=james@wellbehavedsoftware.com \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=mark@fasheh.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).