From: Filipe David Borba Manana <fdmanana@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Filipe David Borba Manana <fdmanana@gmail.com>
Subject: [PATCH 4/4 v2] Btrfs-progs: add write and clone commands debug info to receive
Date: Wed, 16 Apr 2014 15:58:50 +0100 [thread overview]
Message-ID: <1397660330-8155-1-git-send-email-fdmanana@gmail.com> (raw)
In-Reply-To: <1397580051-26643-4-git-send-email-fdmanana@gmail.com>
When specifying -vv print information about received write and clone commands too,
as we do this for other commands already and it's very useful for debugging and
troubleshooting.
Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
---
V2: Added new send ioctl flag BTRFS_SEND_FLAG_SUPPORT_FALLOCATE. A version 2
stream is now only produced is the ioctl caller specifies at least one of
the new send flags (BTRFS_SEND_FLAG_SUPPORT_FALLOCATE or
BTRFS_SEND_FLAG_CALCULATE_DATA_SIZE).
cmds-receive.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/cmds-receive.c b/cmds-receive.c
index 3f30066..7a23823 100644
--- a/cmds-receive.c
+++ b/cmds-receive.c
@@ -636,6 +636,10 @@ static int process_write(const char *path, const void *data, u64 offset,
u64 pos = 0;
int w;
+ if (g_verbose >= 2)
+ fprintf(stderr, "write %s, offset %llu, len %llu\n",
+ path, offset, len);
+
ret = open_inode_for_write(r, full_path);
if (ret < 0)
goto out;
@@ -672,6 +676,11 @@ static int process_clone(const char *path, u64 offset, u64 len,
char *full_clone_path = NULL;
int clone_fd = -1;
+ if (g_verbose >= 2)
+ fprintf(stderr,
+ "clone %s, offset %llu, len %llu, clone path %s, clone offset %llu\n",
+ path, offset, len, clone_path, clone_offset);
+
ret = open_inode_for_write(r, full_path);
if (ret < 0)
goto out;
--
1.9.1
next prev parent reply other threads:[~2014-04-16 13:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 16:40 [PATCH 1/4] Btrfs-progs: send, bump stream version Filipe David Borba Manana
2014-04-15 16:40 ` [PATCH 2/4] Btrfs-progs: send, implement total data size callback and progress report Filipe David Borba Manana
2014-04-16 14:56 ` [PATCH 2/4 v2] " Filipe David Borba Manana
2014-04-16 17:43 ` David Sterba
2014-04-16 18:07 ` Filipe David Manana
2014-04-16 19:57 ` [PATCH 2/4 v3] " Filipe David Borba Manana
2014-04-20 14:10 ` [PATCH 2/4 v4] " Filipe David Borba Manana
2014-04-15 16:40 ` [PATCH 3/4] Btrfs-progs: send, implement fallocate command callback Filipe David Borba Manana
2014-04-16 14:57 ` [PATCH 3/4 v2] " Filipe David Borba Manana
2014-04-16 19:58 ` [PATCH 3/4 v3] " Filipe David Borba Manana
2014-04-18 17:41 ` David Sterba
2014-04-18 20:02 ` Filipe David Manana
2014-04-20 14:12 ` [PATCH 3/4 v4] " Filipe David Borba Manana
2014-04-15 16:40 ` [PATCH 4/4] Btrfs-progs: add write and clone commands debug info to receive Filipe David Borba Manana
2014-04-16 14:58 ` Filipe David Borba Manana [this message]
2014-04-16 14:54 ` [PATCH 1/4 v2] Btrfs-progs: send, bump stream version Filipe David Borba Manana
2014-04-20 14:09 ` [PATCH 1/4 v3] " Filipe David Borba Manana
2014-05-02 15:22 ` [PATCH 1/4] " David Sterba
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=1397660330-8155-1-git-send-email-fdmanana@gmail.com \
--to=fdmanana@gmail.com \
--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 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).