From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>, Eric Mesa <eric@ericmesa.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Issues with btrfs send/receive with parents
Date: Tue, 11 Jun 2019 06:39:53 +0300 [thread overview]
Message-ID: <9d9f4b67-57c1-2003-8e15-52e8460c3c9d@gmail.com> (raw)
In-Reply-To: <CAJCQCtSLVxVtArLHrx0XD6J1oWOowqAnOPzeWVx3J25O7vxFQw@mail.gmail.com>
11.06.2019 4:10, Chris Murphy пишет:
>
> It's most useful if you show exact commands because actually it's not
> always obvious to everyone what the logic should be and the error
> handling doesn't always stop a user from doing something that doesn't
> make a lot of sense. We need to know the name of the rw subvolume; the
> command to snapshot it; the full send/receive command for that first
> snapshot; the command for a subsequent snapshot; and the command to
> incrementally send/receive it.
>
>
And the actual output of each command, not description what user thinks
has happened.
next prev parent reply other threads:[~2019-06-11 3:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 23:56 Issues with btrfs send/receive with parents Eric Mesa
2019-06-11 1:10 ` Chris Murphy
2019-06-11 3:39 ` Andrei Borzenkov [this message]
2019-06-11 4:19 ` Eric Mesa
2019-06-12 5:43 ` Andrei Borzenkov
2019-06-12 23:03 ` Eric Mesa
2019-06-12 23:11 ` Eric Mesa
2019-06-13 6:26 ` Andrei Borzenkov
2019-06-13 21:22 ` Eric Mesa
2019-06-14 3:55 ` Chris Murphy
2019-07-14 20:59 ` Eric Mesa
2019-06-18 4:15 ` Andrei Borzenkov
2019-06-11 3:47 ` Eric Mesa
2019-06-11 1:11 ` Remi Gauvin
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=9d9f4b67-57c1-2003-8e15-52e8460c3c9d@gmail.com \
--to=arvidjaar@gmail.com \
--cc=eric@ericmesa.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).