From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream.
Date: Sat, 23 Jan 2016 16:48:26 -0700 [thread overview]
Message-ID: <CAJCQCtRyyu3rdyyykEjf8neLh3R+12to_gcCpU2ss51dU-_7PA@mail.gmail.com> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=111221
4.4.0-1.fc24.x86_64
btrfs-progs-4.3.1-1.fc23.x86_64
[...snip...]
BTRFS_IOC_SEND returned 0
joining genl thread
At subvol testsub.1
ERROR: parent determination failed for 0
chown temp/cockpit-shell-0.91-1.fc23.noarch.rpm - uid=0, gid=0
chmod temp/cockpit-shell-0.91-1.fc23.noarch.rpm - mode=0644
utimes temp/cockpit-shell-0.91-1.fc23.noarch.rpm
mkfile o270-134474-0
rename o270-134474-0 -> temp/cockpit-networkmanager-0.91-1.fc23.noarch.rpm
utimes temp
set_xattr temp/cockpit-networkmanager-0.91-1.fc23.noarch.rpm -
name=security.selinux data_len=38
data=unconfined_u:object_r:admin_home_t:s0
truncate temp/cockpit-networkmanager-0.91-1.fc23.noarch.rpm size=37322
chown temp/cockpit-networkmanager-0.91-1.fc23.noarch.rpm - uid=0, gid=0
chmod temp/cockpit-networkmanager-0.91-1.fc23.noarch.rpm - mode=0644
utimes temp/cockpit-networkmanager-0.91-1.fc23.noarch.rpm
ERROR: unexpected EOF in stream.
The same ERROR messages happens even if I use -p to specify the parent.
Sending conventionally one at a time with -p works OK.
--
Chris Murphy
next reply other threads:[~2016-01-23 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 23:48 Chris Murphy [this message]
2016-01-23 23:55 ` [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream Hugo Mills
2016-01-24 0:08 ` Chris Murphy
2016-01-24 0:12 ` Chris Murphy
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=CAJCQCtRyyu3rdyyykEjf8neLh3R+12to_gcCpU2ss51dU-_7PA@mail.gmail.com \
--to=lists@colorremedies.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).