From owner-freebsd-fs@FreeBSD.ORG Fri Jul 25 16:04:04 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6212AB20; Fri, 25 Jul 2014 16:04:04 +0000 (UTC) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) by mx1.freebsd.org (Postfix) with ESMTP id E16032159; Fri, 25 Jul 2014 16:04:03 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3hKZwK37dSz1Fl; Fri, 25 Jul 2014 18:04:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla2; t=1406304237; x=1408896238; bh=5tU xIkHU41RaDcB2wIFMAbcYiWVzkkWlF3LWCpOJ/hY=; b=o92OJgw8PAAXl0G6p5X rHDOoT2rKFMDC+uF9/FL1NaVqKfGCbKn/3HMhDC6pyScpxgRdwXnt5vk5lw9gg7i MC4yUCrc9oUkXNwwndWr97+r4gtsgL37kIzA3BOlp1ngOJgffYC3Hvg6l8eYEUY/ SSe4+A9/V85B91FMOvCLu33Y= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10012) with ESMTP id Ao8VxMVqEYjR; Fri, 25 Jul 2014 18:03:57 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP; Fri, 25 Jul 2014 18:03:57 +0200 (CEST) Received: from neli.ijs.si (neli.ijs.si [IPv6:2001:1470:ff80:88:21c:c0ff:feb1:8c91]) by mildred.ijs.si (Postfix) with ESMTP id 3hKZwF2rQCzVN; Fri, 25 Jul 2014 18:03:57 +0200 (CEST) Received: from neli.ijs.si ([2001:1470:ff80:88:21c:c0ff:feb1:8c91]) by neli.ijs.si with HTTP (HTTP/1.1 POST); Fri, 25 Jul 2014 18:03:57 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 25 Jul 2014 18:03:57 +0200 From: Mark Martinec To: freebsd-current@freebsd.org, Freebsd fs Subject: Re: zfs send/recv: STILL invalid Backup Stream Organization: J. Stefan Institute In-Reply-To: <20140725134125.GA19293@thebighonker.lerctr.org> References: <3d2aac84d962a703fbf56a864ba5f19c@mailbox.ijs.si> <9eef3e7e964cb33fd163cc2f9300f326@mailbox.ijs.si> <53D1AB3D.1060205@freebsd.org> <33c478c3120c21d6cb9c325cc1119cf8@thebighonker.lerctr.org> <60845088153247fa31c50c9f52ef72cb@mailbox.ijs.si> <20140725134125.GA19293@thebighonker.lerctr.org> Message-ID: <2f191a3e72b9d94a15128de806f8d1c8@mailbox.ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.0.1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2014 16:04:04 -0000 2014-07-25 15:41, Larry Rosenman wrote: > On Fri, Jul 25, 2014 at 11:58:48AM +0200, Mark Martinec wrote: >> Don't know, I'd guess some network-related memory limit is being hit >> on the sending site. >> >> Why not try to decouple the 'zfs send' from a network copy and ssh: >> Login to a remote side, do a 'zfs send' to some local temporary file >> there, then feed that file to ssh and send it over to a home host, >> where it can be piped into some simple program like md5 or 'wc -c' >> instead of a zfs recv. >> > I think I've done that, but it sort of defeats the purpose, Does it? If you are lucky it would fail again, but this time you'd know if it was a zfs or a network problem. > as the stream becomes a big file on disk. If it's an incremental stream and you have sufficient free space available, than it's all fine and you should try that. If storage is a problem you may try piping /dev/zero or /dev/random through ssh to feed a remote consumer, simulating a huge stream, and hope that it will eventually fail. > I'd like to get some help chasing what parameter(s) need to be fixed > here. [...] > Can I get some ideas on: > 1) what MIGHT need tweaking > 2) would (k|d)trace help? > 3) what else could we find out what's being told no memory? Sorry, not deep enough into fs or network to be able to tell. My guess it that it's a networking issue (not zfs), and not directly related to virtual memory or swap or ARC management. > To: freebsd-current@freebsd.org, Freebsd fs If you'd be able to demonstrate that this is unrelated to zfs, then the freebsd-net@freebsd.org mailing list would perhaps be a suitable place to continue this thread. Mark