Hey Qu, On Fri, 30 Dec 2016 08:47:07 +0800 Qu Wenruo <quwenruo@xxxxxxxxxxxxxx> wrote: > Hi Glenn, > > Confirmed it's kernel bug. > Send stream doesn't contain the clone operation. > > So it's kernel send to blame. > > > > > As I was using btrgs-progs v4.4, I've compiled v4.9 to get the nice > > --dump option for receive (which you seem to have added, kudos!). > > The output of the dump option is in the *.recv-dump.log files. > > However, I see no clone command in the output. > > > > Keep in mind that I'm running Ubuntu kernel 4.4.0-53-generic, which > > I believe to be mostly v4.4.30 with a few patches. Any ideas when > > send started using "clone" in the kernel? > > Not pretty sure about from which exact kernel version send can detect > reflink. > > AFAIC I sent an RFC patch to disable reflink detection in send in > July 2016, and it just got rejected. > > So I assume at least v4.6 kernel works. I've tested with Ubuntu's 4.8 kernel and still no luck. What kernel version are you using? And what version of btrfs-progs? If I understand you correctly, you're trying to submit a patch that disables reflink detection, which would prevent what I'm trying to do? Why is this desired and is it able to be switched off? Thanks, Glenn -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
