zfs discuss - Mar 2012 - Receive failing with "invalid backup stream" error

Hello,

I am problems sending some snapshots between two fully up to date 
Solaris 11 systems:

zfs send -i tank/live/fs at 20120226_0705 tank/live/fs at 20120226_1105 | ssh 
remote zfs receive -vd fileserver/live
receiving incremental stream of tank/live/fs at 20120226_1105 into 
fileserver/live/fs at 20120226_1105
cannot receive incremental stream: invalid backup stream

Both pools and filesystems are at the latest revision.  Most the other 
filesystems in the pool can be sent without issues.

The filesystem was upgraded yesterday, which is when the problems 
stared.  The snapshots are from 26/02.

Other filesystems that were upgraded yesterday receive fine, so I don''t
think the problem is directly related to the upgrade.

Any ideas?

-- 
Ian.

On 03/ 3/12 11:57 AM, Ian Collins wrote:
> Hello,
>
> I am problems sending some snapshots between two fully up to date
> Solaris 11 systems:
>
> zfs send -i tank/live/fs at 20120226_0705 tank/live/fs at 20120226_1105 |
ssh
> remote zfs receive -vd fileserver/live
> receiving incremental stream of tank/live/fs at 20120226_1105 into
> fileserver/live/fs at 20120226_1105
> cannot receive incremental stream: invalid backup stream
>
> Both pools and filesystems are at the latest revision.  Most the other
> filesystems in the pool can be sent without issues.
>
> The filesystem was upgraded yesterday, which is when the problems
> stared.  The snapshots are from 26/02.
>
> Other filesystems that were upgraded yesterday receive fine, so I
don''t
> think the problem is directly related to the upgrade.
>
> Any ideas?
>
I haven''t had a solution from support yet, but I do have a workaround
if
anyone else encounters the same problem.

I sent the snapshot to a file, coped the file to the remote host and 
piped the file into zfs receive.  That worked and I was able to send 
further snapshots with ssh.

Odd.

-- 
Ian.

2012-03-09 9:24, Ian Collins wrote:
> I sent the snapshot to a file, coped the file to the remote host and
> piped the file into zfs receive. That worked and I was able to send
> further snapshots with ssh.
>
> Odd.
Is it possible that in case of "zfs send ... | ssh | zfs recv"
piping, the two ZFS processes can have some sort of dialog and
misunderstanding in your case; while zfs-sending to a file has
no dialog and some commonly-working default format/assumptions?

As a wild guess, two systems might have different opinions for
example regarding dedup during dialog, while it was not even
considered when passing through files?

//Jim

On 03/10/12 01:48 AM, Jim Klimov wrote:
> 2012-03-09 9:24, Ian Collins wrote:
>> I sent the snapshot to a file, coped the file to the remote host and
>> piped the file into zfs receive. That worked and I was able to send
>> further snapshots with ssh.
>>
>> Odd.
> Is it possible that in case of "zfs send ... | ssh | zfs recv"
> piping, the two ZFS processes can have some sort of dialog and
> misunderstanding in your case; while zfs-sending to a file has
> no dialog and some commonly-working default format/assumptions?
>
> As a wild guess, two systems might have different opinions for
> example regarding dedup during dialog, while it was not even
> considered when passing through files?
Both systems are identical (same hardware, same SRU).

The receive also fails if the output of the libzfs zfs_send() function 
is connected through a socket to zfs_receive() on the other box.
-- 
Ian.