From owner-freebsd-questions@freebsd.org Mon Jul 17 19:33:52 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50693D9EDB3 for ; Mon, 17 Jul 2017 19:33:52 +0000 (UTC) (envelope-from 482254ac@razorfever.net) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.181]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "*.teksavvy.com", Issuer "DigiCert High Assurance CA-3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DA0886E7E1 for ; Mon, 17 Jul 2017 19:33:51 +0000 (UTC) (envelope-from 482254ac@razorfever.net) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0D/FgBvEG1Z/0StpUVcGwEBAQMBAQEJAQEBgj2BHSo9kA+PPAEBAQEBBQGBJDABl2gciHNEFAECAQEBAQEBAWsohUIVHlgCJgI7LgMIAQGKHg2vfYImiziBC4IdgwaCU4gvgkeCYQEEgjCHGA2HAYFghQyHcQECnzERhwGUE4FENiGBChwtN4UWAQsBgmIkiUIBAQE X-IPAS-Result: A0D/FgBvEG1Z/0StpUVcGwEBAQMBAQEJAQEBgj2BHSo9kA+PPAEBAQEBBQGBJDABl2gciHNEFAECAQEBAQEBAWsohUIVHlgCJgI7LgMIAQGKHg2vfYImiziBC4IdgwaCU4gvgkeCYQEEgjCHGA2HAYFghQyHcQECnzERhwGUE4FENiGBChwtN4UWAQsBgmIkiUIBAQE X-IronPort-AV: E=Sophos;i="5.40,375,1496116800"; d="scan'208";a="320527385" Received: from 69-165-173-68.dsl.teksavvy.com (HELO mail.razorfever.net) ([69.165.173.68]) by smtp.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Jul 2017 15:32:42 -0400 Received: from [127.0.0.1] (mail.razorfever.net [192.168.0.4]) by mail.razorfever.net (8.15.2/8.14.9) with ESMTP id v6HJWe3F063426 for ; Mon, 17 Jul 2017 15:32:41 -0400 (EDT) (envelope-from 482254ac@razorfever.net) X-Authentication-Warning: mail.razorfever.net: Host mail.razorfever.net [192.168.0.4] claimed to be [127.0.0.1] To: freebsd-questions@freebsd.org From: "Derek (freebsd lists)" <482254ac@razorfever.net> Subject: zfs send -R | zfs recv aborted Message-ID: Date: Mon, 17 Jul 2017 15:32:40 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.4 required=5.0 tests=ALL_TRUSTED, FROM_STARTS_WITH_NUMS,RP_MATCHES_RCVD autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.razorfever.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2017 19:33:52 -0000 Hiya! Wondering if anyone can help give me pointers, or has a rough idea where to look next. The situation is this: I've got a 10.2-RELEASE sender, and a 10.3-RELEASE receiver. I'm trying so send a ~20TB recursive dataset over gig-e. I've had a failed send because the ssh connection is torn down (for reasons unknown), and a second failed attempt because the zfs send command went (a child of sudo). Usually the transfer fails after a few days (14TB+) of copying. I'm confident in the hardware. My thinking is, most of the filesystems+snapshots that are already showing up on the receive side are successful. If possible, I'd like to keep the correctly-received filesystems+snapshots, and free up the resources from the ones that haven't been correctly received. Then I will transfer the rest by name (i.e. not recursively). The send-resume in 10.3 would be fabulous here, but I'm running out of time, and I'd really rather avoid a restart. I've been playing around with zdb to try to compare what's missing/incomplete, but the manual page doesn't really give me much information on how to understand the detailed information returned. Does anyone have: - an alternative approach or - a way to free the resources by an incomplete receive, without trashing the rest of the receive or - a resource that will help me grok zdb output such that I could write something that will be able to give me the value I seek Thanks Derek