Re: ZFS: Invalid SEND/RECV stream still

On 2013-10-25 12:33, Ian Lepore wrote:
> On Fri, 2013-10-25 at 12:07 -0500, Larry Rosenman wrote:
>> between 10.0-BETA1 and 11.0-CURRENT.
>> I've been fighting this battle for a LONG time.  I had hoped(!) that 
>> it
>> would be solved by the systems being
>> closer in rev but that didn't happen.
>> 
>> I'd LOVE someone to look at it.
>> 
>> I can provide ssh / root access to both machines.
>> 
>> 
>> Error Message:
>> received 320KB stream in 1 seconds (320KB/sec)
>> receiving incremental stream of vault/var_at_2013-10-25 into
>> zroot/backups/TBH/var_at_2013-10-25
>> cannot receive incremental stream: invalid backup stream
>> $
>> 
>> Script:
>> $ cat backup-TBH-ZFS.sh
>> #!/bin/sh
>> DATE=`date "+%Y-%m-%d"`
>> #DATE2=2013-03-24
>> DATE2=`date -v "-1d" "+%Y-%m-%d"`
>> # snap the source
>> ssh root_at_tbh.lerctr.org zfs snapshot -r vault_at_${DATE}
>> # zfs copy the source to here.
>> ssh root_at_tbh.lerctr.org "zfs send  -R -D  -I vault_at_${DATE2}
>> vault_at_${DATE} | \
>>       ssh home.lerctr.org \"zfs recv -F -u -v -d zroot/backups/TBH\""
>> # make sure we NEVER allow the backup stuff to automount.
>> /sbin/zfs list -H -t filesystem -r zroot/backups/TBH| \
>>      awk '{printf "/sbin/zfs set canmount=noauto %s\n",$1}' | sh
>> $
>> 
>> Uname's:
>> $ uname -a
>> FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #80 r257016:
>> Wed Oct 23 17:36:15 CDT 2013
>> root_at_borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE  amd64
>> $ ssh tbh uname -a
>> FreeBSD thebighonker.lerctr.org 10.0-BETA1 FreeBSD 10.0-BETA1 #1
>> r256791: Sun Oct 20 12:28:55 CDT 2013
>> root_at_thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER  amd64
>> $
>> 
>> What else do y'all need?
>> 
>> 
>> 
> 
> I notice you're using ssh and a pipe -- does your shell logon script
> echo anything to stdout when you connect?  I've had that interfere with
> piped ssh stuff.  Most shells provide a way for the logon script to
> determine "is this an interactive session?" and you can use that to
> avoid echoing anything that would interfere with non-interactive
> automation.
> 
> -- Ian
no, it does NOT.

I've verified that, plus this error is a LONG way into the stream.  (I 
cut a bunch
of the previous output).

I've even gathered tmp files from this before, but no one had the time
to look at it.

Thanks for at least looking.


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c)     E-Mail: ler_at_lerctr.org
US Mail: 108 Turvey Cove, Hutto, TX 78634-5688