From: Josef Bacik <jbacik@fusionio.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: <linux-btrfs@vger.kernel.org>, <dsterba@suse.cz>, <jeff.liu@oracle.com>
Subject: Re: [PATCH] Btrfs: export btrfs space shared info to userspace
Date: Wed, 18 Sep 2013 16:53:04 -0400 [thread overview]
Message-ID: <20130918205304.GA1615@localhost.localdomain> (raw)
In-Reply-To: <1379317212-20246-1-git-send-email-bo.li.liu@oracle.com>
On Mon, Sep 16, 2013 at 03:40:12PM +0800, Liu Bo wrote:
> Similar to ocfs2, btrfs also supports that extents can be shared by
> different inodes, and there are some userspace tools requesting
> for this kind of 'space shared infomation'.[1]
>
> ocfs2 uses flag FIEMAP_EXTENT_SHARED, so does btrfs.
>
> [1]: http://thr3ads.net/ocfs2-devel/2010/09/489052-PATCH-3-3-shared-du-using-fiemap-to-figure-up-the-shared-extents-per-file-and-the-footprint-in
>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> ---
> RFC->PATCH: use type 'unsigned long' instead of 'int', as David suggested.
This broke any xfstest that used fiemap, so generic/255, generic/316 and
shared/218. Thanks,
Josef
next prev parent reply other threads:[~2013-09-18 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 7:40 [PATCH] Btrfs: export btrfs space shared info to userspace Liu Bo
2013-09-18 20:53 ` Josef Bacik [this message]
2013-09-20 0:22 ` Liu Bo
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=20130918205304.GA1615@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=jeff.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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).