btrfs send -p

Hi guys, It seems that btrfs v4.12.1 allows: (1) btrfs send -p but disallows (2) btrfs send -p Code-wise it assumes that is always found at optind == 1. I was about to patch this but I'm not sure which way we'd like to go with this: Actually only allow (1) and block (2)

Re: [PATCH 1/1] btrfs-progs: send: fail on first -ENODATA only

Hi, The original bug-reporter verified that my patch fixes the bug. See https://bugzilla.kernel.org/show_bug.cgi?id=195597 Christian On Sat, Apr 29, 2017 at 11:54:05PM +0200, Christian Brauner wrote: > Returning -ENODATA is only considered invalid on the first run of the loop. > > S

[PATCH 1/1] btrfs-progs: send: fail on first -ENODATA only

Returning -ENODATA is only considered invalid on the first run of the loop. Signed-off-by: Christian Brauner <christian.brau...@ubuntu.com> --- cmds-receive.c | 20 ++-- 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/cmds-receive.c b/cmds-receive.c index b5

[PATCH 0/1] btrfs-progs: send: fail on first -ENODATA only

Christian Brauner (1): btrfs-progs: send: fail on first -ENODATA only cmds-receive.c | 20 ++-- 1 file changed, 14 insertions(+), 6 deletions(-) -- 2.11.0 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message

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

NODATA is returned with this patch it should mean that there was no header data. So is the user sure that this doesn't indicate a valid error? Christian > > > Cheers, > Lakshmipathi.G > > > On Tue, Apr 4, 2017 at 1:51 AM, Christian Brauner < > christian.brau...@ubuntu.c

Prevent escaping btrfs quota

Hi guys, If a qgroup is created for a btrfs subvolume /some/path and limits are set and a new btrfs subvolume /some/path/bla is created it does not inherit the parent subvolume's /some/path qgroup and limits. The only way to achieve something similar is to create a common "parent" qgroup and

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

that they will lack is a nice error message. Signed-off-by: Christian Brauner <christian.brau...@ubuntu.com> --- Changelog: 2017-04-03 - no changes --- cmds-receive.c | 13 + send-stream.c | 2 +- 2 files changed, 6 insertions(+), 9 deletions(-) diff --git a/cmds-receive.c

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

that they will lack is a nice error message. Christian Brauner (2): btrfs-progs: fix btrfs send & receive with -e flag tests: use receive -e to terminate on end marker cmds-receive.c | 13 + send-stream.c

[PATCH 2/2 v2] tests: use receive -e to terminate on end marker

Signed-off-by: Christian Brauner <christian.brau...@ubuntu.com> --- tests/misc-tests/018-recv-end-of-stream/test.sh | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tests/misc-tests/018-recv-end-of-stream/test.sh b/tests/misc-tests/018-recv-end-of-stream/t

Re: [PATCH] btrfs-progs: fix btrfs send & receive with -e flag

Hi guys, Friendly ping. Just checking in on this patch since I haven't heard back so far and this is a blocker in some scenarios where we're using btrfs. Thanks! Christian On Fri, Mar 24, 2017 at 04:00:57PM +0100, Christian Brauner wrote: > The old check here tried to ensure that empty stre

[PATCH] btrfs-progs: fix btrfs send & receive with -e flag

that they will lack is a nice error message. Signed-off-by: Christian Brauner <christian.brau...@ubuntu.com> --- cmds-receive.c | 13 + send-stream.c | 2 +- 2 files changed, 6 insertions(+), 9 deletions(-) diff --git a/cmds-receive.c b/cmds-receive.c index 6cf22637..b59f00e4