From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: send, fix some failures due to commands with wrong paths
Date: Mon, 21 Sep 2020 14:13:28 +0100 [thread overview]
Message-ID: <cover.1600693246.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Incremental send operations can often fail at the receiver due to a wrong
path in some command. This small patchset fixes a few more cases where
such problems happen. There are sporadic reports of this type of failures,
such as [1] and [2] for example, and many similar issues were fixed in a
more distant past. Without having the full directory trees of the parent
and send snapshots, with inode numbers, it's hard to tell if this patchset
fixes exactly those reported cases, but the cases fixed by this patchset
are all I could find in the last two weeks.
[1] https://lore.kernel.org/linux-btrfs/57021127-01ea-6533-6de6-56c4f22c4a5b@gmail.com/
[2] https://lore.kernel.org/linux-btrfs/87a7obowwn.fsf@lausen.nl/
Filipe Manana (2):
btrfs: send, orphanize first all conflicting inodes when processing
references
btrfs: send, recompute reference path after orphanization of a
directory
fs/btrfs/send.c | 200 ++++++++++++++++++++++++++++++++++++++----------
1 file changed, 160 insertions(+), 40 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-21 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 13:13 fdmanana [this message]
2020-09-21 13:13 ` [PATCH 1/2] btrfs: send, orphanize first all conflicting inodes when processing references fdmanana
2020-09-21 13:13 ` [PATCH 2/2] btrfs: send, recompute reference path after orphanization of a directory fdmanana
2020-09-21 14:29 ` [PATCH 0/2] btrfs: send, fix some failures due to commands with wrong paths Josef Bacik
2020-09-23 12:46 ` David Sterba
2020-09-23 14:25 ` Johannes Thumshirn
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=cover.1600693246.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.