linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert White <rwhite@pobox.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Can't cp --reflink files on a Ext4-converted FS w/o checksums
Date: Thu, 27 Nov 2014 23:12:56 -0800	[thread overview]
Message-ID: <54782078.1010700@pobox.com> (raw)
In-Reply-To: <pan$38a8e$6ec3447a$892ad9ec$128580b7@cox.net>

On 11/27/2014 01:27 AM, Duncan wrote:
> Robert White posted on Wed, 26 Nov 2014 15:18:26 -0800 as excerpted:
>
>> I also don't see anything in the code that says "this ioctl will create
>> the checksums for the selected file" so you may have to do the copy you
>> tried to avoid.
> Note that btrfs check has an --init-csum-tree switch.

I thought about that, but I doubt it's going to go through all the 
inodes and clear the NODATASUM bit from the inode flags where it's been 
set by something such as the conversion using -d or setting the 
NODATACOW flag (e.g. the +C attribute).

So while that will, hopefully, recalculate the checksums on the regular 
files I don't think it would have fixed his problem since those files 
weren't "regular" at that point.


  reply	other threads:[~2014-11-28  7:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 19:55 Can't cp --reflink files on a Ext4-converted FS w/o checksums Roman Mamedov
2014-11-26 23:18 ` Robert White
2014-11-26 23:33   ` Roman Mamedov
2014-11-27  0:00     ` Robert White
2014-11-27  0:20       ` Roman Mamedov
2014-11-27  0:31         ` Robert White
2014-11-27  0:57           ` Robert White
2014-11-27  0:20     ` Robert White
2014-11-27  0:28       ` Roman Mamedov
2014-11-27  0:45         ` Robert White
2014-11-27  9:27   ` Duncan
2014-11-28  7:12     ` Robert White [this message]
2014-11-27  3:31 ` 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=54782078.1010700@pobox.com \
    --to=rwhite@pobox.com \
    --cc=1i5t5.duncan@cox.net \
    --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).