From owner-freebsd-current@FreeBSD.ORG  Fri Oct 25 19:33:10 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 4D86925C
 for <current@freebsd.org>; Fri, 25 Oct 2013 19:33:10 +0000 (UTC)
 (envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu
 (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0BEDC2C8B
 for <current@freebsd.org>; Fri, 25 Oct 2013 19:33:09 +0000 (UTC)
Received: from hergotha.csail.mit.edu (localhost [127.0.0.1])
 by hergotha.csail.mit.edu (8.14.5/8.14.5) with ESMTP id r9PJX8Um086598;
 Fri, 25 Oct 2013 15:33:08 -0400 (EDT)
 (envelope-from wollman@hergotha.csail.mit.edu)
Received: (from wollman@localhost)
 by hergotha.csail.mit.edu (8.14.5/8.14.4/Submit) id r9PJX8sx086597;
 Fri, 25 Oct 2013 15:33:08 -0400 (EDT) (envelope-from wollman)
Date: Fri, 25 Oct 2013 15:33:08 -0400 (EDT)
From: Garrett Wollman <wollman@hergotha.csail.mit.edu>
Message-Id: <201310251933.r9PJX8sx086597@hergotha.csail.mit.edu>
To: current@freebsd.org
Subject: Re: ZFS: Invalid SEND/RECV stream still
References: <c0a42b456769e22f908e689a1de56c82@webmail.lerctr.org>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (hergotha.csail.mit.edu [127.0.0.1]); Fri, 25 Oct 2013 15:33:08 -0400 (EDT)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED
 autolearn=disabled version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
 hergotha.csail.mit.edu
X-Mailman-Approved-At: Fri, 25 Oct 2013 19:44:31 +0000
Cc: ler@lerctr.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 19:33:10 -0000

In article <c0a42b456769e22f908e689a1de56c82@webmail.lerctr.org>,
Larry Rosenman  <ler@lerctr.org> wrote:

>Error Message:
>received 320KB stream in 1 seconds (320KB/sec)
>receiving incremental stream of vault/var@2013-10-25 into 
>zroot/backups/TBH/var@2013-10-25
>cannot receive incremental stream: invalid backup stream

I've seen this happen in one very specific case: if the receiving
machine is doing automatic snapshots, and happens to do a snapshot of
the filesystem being received *while it's being received*.  In that
case, it appears that the filesystem on disk gets subtly corrupted,
and the only remedy is to destroy it on the receiving machine and
start all over (making sure to disable automatic snapshots this time).

"zfs receive -F" will rollback snapshots made on the receiving system
that don't exist on the sending system, but it only does this at the
beginning of the stream -- it can't prevent further snapshots from
being taken during reception of an incremental stream which foul up
the works.

-GAWollman