linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream.
Date: Sat, 23 Jan 2016 23:55:36 +0000	[thread overview]
Message-ID: <20160123235536.GZ422@carfax.org.uk> (raw)
In-Reply-To: <CAJCQCtRyyu3rdyyykEjf8neLh3R+12to_gcCpU2ss51dU-_7PA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]

On Sat, Jan 23, 2016 at 04:48:26PM -0700, Chris Murphy wrote:
> 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

   This looks to me like a known and somewhat awkward bug/misfeature
where the mountpoint containing either the subvol being sent or the
target location for the receive is not a top-level mount, which causes
this error. i.e., this will (I think) fail:

# mount -o subvol=@foo /dev/sda1 /mnt
# btrfs send /mnt/@whatever | ...

   Can you try again from within a subvolid=0 mount?

   Hugo.

> 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.
> 
> 

-- 
Hugo Mills             | Great films about cricket: The Third Man
hugo@... carfax.org.uk |
http://carfax.org.uk/  |
PGP: E2AB1DE4          |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-01-23 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23 23:48 [bug] btrfs send -e option always fails ERROR: unexpected EOF in stream Chris Murphy
2016-01-23 23:55 ` Hugo Mills [this message]
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=20160123235536.GZ422@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --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).