From: " " <Cedric.dewijs@eclipso.eu>
To: "Roman Mamedov" <rm@romanrm.net>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Re: btrfs send / receive via netcat, fails halfway?
Date: Sun, 10 Jan 2021 13:38:26 +0100 [thread overview]
Message-ID: <f1151bac14674472000b788fdcfe0d53@mail.eclipso.de> (raw)
In-Reply-To: <20210110163705.1852c4a7@natsu>
It is a common annoyance that NC doesn't exit in such scenario and needs
to be
Ctrl-C'ed after verifying that the transfer is over.
Instead, at host2 try:
ssh host1 "btrfs send ..." | btrfs receive ...
Also much more secure.
--
With respect,
Roman
I was practicing on a test system, the real transfer was supposed to be between two systems on a LAN. I didn't want encryption, as my system then only is capable of sending 30MB/sec, instead of the 110MB/sec over the 1GB network.
---
Take your mailboxes with you. Free, fast and secure Mail & Cloud: https://www.eclipso.eu - Time to change!
next prev parent reply other threads:[~2021-01-10 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 10:34 btrfs send / receive via netcat, fails halfway?
2021-01-10 11:07 ` Forza
2021-01-10 11:37 ` Roman Mamedov
2021-01-10 12:38 ` [this message]
2021-01-10 11:47 ` Hugo Mills
2021-01-10 13:27 ` Hugo Mills
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=f1151bac14674472000b788fdcfe0d53@mail.eclipso.de \
--to=cedric.dewijs@eclipso.eu \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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