public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Jian Lin <lj@linjian.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: A file cloned with "--reflink" different from the original one?
Date: Mon, 23 Nov 2009 09:40:20 -0500	[thread overview]
Message-ID: <20091123144019.GA15294@think> (raw)
In-Reply-To: <119341710911230126t542b7921p9dd15d804ba97244@mail.gmail.com>

On Mon, Nov 23, 2009 at 05:26:32PM +0800, Jian Lin wrote:
> I installed BtrFS 0.19 and GNU coreutils 8.1 on my Ubuntu 9.10.
> I tried to clone some files with "--reflink" to make them "copy-on-write".
> However, I found some of the files cloned have different MD5's to the
> original ones.
> 
> Is BtrFS (or cp with reflink) buggy?
> Or it is indeed a feature that I used incorrectly?

There have been some fixes to the reflink code sine 2.6.31, I think
you're hitting a known bug.  Please try the btrfs-unstable repo, or a
2.6.32-rc kernel.

-chris

      reply	other threads:[~2009-11-23 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23  9:26 A file cloned with "--reflink" different from the original one? Jian Lin
2009-11-23 14:40 ` Chris Mason [this message]

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=20091123144019.GA15294@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lj@linjian.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