ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Gang He <ghe@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] About the status of reflink-tools
Date: Mon, 1 Feb 2021 11:42:52 +0800	[thread overview]
Message-ID: <34a041e3-1db5-d8fe-f683-08978f23ebf9@suse.com> (raw)
In-Reply-To: <e0d299d1-21f1-0738-ff73-7cc3031cd581@oracle.com>

Hi Wengang,

Thank for your information.
According to Darrick's mail, the reflink related tools have been merged 
into coreutils project, that means we can forget reflink-tools project.

Thanks
Gang

On 2021/1/30 2:34, Wengang Wang wrote:
> 
> On 1/28/21 11:46 PM, Gang He wrote:
>> Hi Herbert,
>>
>>
>> On 2021/1/29 15:33, Herbert Van Den Bergh wrote:
>>> Hi Gang,
>>>
>>> The reflink functionality has been merged into the coreutils package/project. The cp command now has a —reflink option. Check it out. If this isn’t what you’re looking for, then please elaborate.
>> For the other tools, e.g. shared-du, shared-filefrag, where do you
>> download the related source code? still coreutils? that means this part
>> code is included/maintained by coreutils project?
>>
>     $ rpm -qi reflink
>     Name        : reflink
>     Version     : 0.1.0
>     Release     : 3.el7
>     Architecture: x86_64
>     Install Date: Mon 21 Sep 2020 05:57:56 PM GMT
>     Group       : System Environment/Kernel
>     Size        : 55003
>     License     : GPL
>     Signature   : RSA/SHA256, Sun 04 May 2014 06:33:00 AM GMT, Key ID
>     72f97b74ec551f03
>     Source RPM  : reflink-0.1.0-3.el7.src.rpm
>     Build Date  : Sun 04 May 2014 06:32:55 AM GMT
>     Build Host  : ca-build56.us.oracle.com
>     Relocations : (not relocatable)
>     Packager    : nobody <nobody@oracle.com>
>     Vendor      : Oracle
>     URL         : http://oss.oracle.com/git/?p=jlbec/reflink.git;a=summary
>     Summary     : Tool to create reflinks on ocfs2/btrfs.
>     Description :
> 
>     The reflink tool creates a reflink on an ocfs2 or a btrfs filesystem.
> 
> Maybe the URL part gives you some idea.
> 
> Cheers,
> Wengang
> 
>> Thanks
>> Gang
>>
>>> Thanks,
>>> Herbert.
>>>
>>>> On Jan 28, 2021, at 6:59 PM, Gang He<GHe@suse.com>  wrote:
>>>>
>>>> Hi Guys,
>>>>
>>>> You know, ocfs2 reflink related utilities were maintained by a seperated project reflink-tools,
>>>> What is this project's status? e.g. who is maintaining it, where can we download the latest source code?
>>>>
>>>>
>>>> Thanks
>>>> Gang
>>>>
>>>> _______________________________________________
>>>> Ocfs2-devel mailing list
>>>> Ocfs2-devel@oss.oracle.com
>>>> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>> _______________________________________________
>> Ocfs2-devel mailing list
>> Ocfs2-devel@oss.oracle.com
>> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel@oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
> 


_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

  reply	other threads:[~2021-02-01  3:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  2:59 [Ocfs2-devel] About the status of reflink-tools Gang He
2021-01-29  7:33 ` Herbert Van Den Bergh
2021-01-29  7:46   ` Gang He
2021-01-29 18:34     ` Wengang Wang
2021-02-01  3:42       ` Gang He [this message]
2021-02-01 17:20         ` Wengang Wang

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=34a041e3-1db5-d8fe-f683-08978f23ebf9@suse.com \
    --to=ghe@suse.com \
    --cc=ocfs2-devel@oss.oracle.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).