Re: [PATCH 1/2 v2] btrfs-progs: fix btrfs send & receive with -e flag

Hi, Sorry for confusion, I've checked once again and the same issue happens in all cases. I didn't notice this because my regular backups are done automatically in cron task + snapshots look fine despite the error, so I incorrectly assumed an error didn't happen there, but it actually did.

Re: [PATCH 1/2 v2] btrfs-progs: fix btrfs send & receive with -e flag

Hi. Adding the bug reporter, Nazar for the discussion (as I'm not familiar with send/receive feature/code). Cheers, Lakshmipathi.G http://www.giis.co.in http://www.webminal.org On Fri, Apr 28, 2017 at 3:25 PM, Christian Brauner wrote: > > Hi, > > On Fri,

Re: [PATCH 1/2 v2] btrfs-progs: fix btrfs send & receive with -e flag

Hi, On Fri, Apr 28, 2017 at 02:55:31PM +0530, Lakshmipathi.G wrote: > Seems like user reported an issue with this patch. please check > https://bugzilla.kernel.org/show_bug.cgi?id=195597 I can take a look. What I'm wondering about is why it fails only in the HDD to SSD case. If -ENODATA is

[PATCH 1/2 v2] btrfs-progs: fix btrfs send & receive with -e flag

The old check here tried to ensure that empty streams are not considered valid. The old check however, will always fail when only one run through the while(1) loop is needed and honor_end_cmd is set. So this: btrfs send /some/subvol | btrfs receive -e /some/ will consistently fail because -e