From: Liu Bo <bo.li.liu@oracle.com>
To: Thomas Koch <thomas@koch.ro>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: check for reflink capability and for shared data
Date: Mon, 26 Aug 2013 17:30:22 +0800 [thread overview]
Message-ID: <20130826093021.GB17457@localhost.localdomain> (raw)
In-Reply-To: <201308241809.58701.thomas@koch.ro>
On Sat, Aug 24, 2013 at 06:09:58PM +0200, Thomas Koch wrote:
> Hi,
>
> how can I do the following in a shell script:
>
> - check whether my file system supports cp --reflink?
> - check whether two files share the same data on disk, i.e. one has been
> created by cp --reflink of the other?
Someone has proposed to teach 'du(1)' to show this, ie. 'du --shared'[1].
It's written for ocfs2 originally, besides btrfs, ocfs2 also can share
data between two files.
[1]: https://oss.oracle.com/pipermail/ocfs2-devel/2010-September/007287.html
-liubo
next prev parent reply other threads:[~2013-08-26 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 16:09 check for reflink capability and for shared data Thomas Koch
2013-08-24 16:20 ` Hugo Mills
2013-08-26 6:42 ` Jan Schmidt
2013-08-26 9:30 ` Liu Bo [this message]
2013-08-27 1:37 ` Marios Titas
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=20130826093021.GB17457@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=thomas@koch.ro \
/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).