From owner-freebsd-fs@FreeBSD.ORG Mon Dec 14 18:46:40 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 448941065679 for ; Mon, 14 Dec 2009 18:46:40 +0000 (UTC) (envelope-from mail@petecurry.net) Received: from gopher.petecurry.net (gopher.petecurry.net [67.18.187.209]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD738FC1B for ; Mon, 14 Dec 2009 18:46:40 +0000 (UTC) Received: from kiwi.petecurry.net (tx-71-48-169-80.dhcp.embarqhsd.net [71.48.169.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pete) by gopher.petecurry.net (Postfix) with ESMTPSA id 20A0D80A147; Mon, 14 Dec 2009 12:26:54 -0600 (CST) Received: by kiwi.petecurry.net (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) mail@petecurry.net; Mon, 14 Dec 2009 12:30:24 -0600 (CST) Date: Mon, 14 Dec 2009 12:30:24 -0600 From: Pete Curry To: Pawel Jakub Dawidek Message-ID: <20091214183024.GM17175@kiwi.petecurry.net> References: <20091029205121.GB3418@garage.freebsd.pl> <9AA2C968-F09D-473D-BD13-F13B3F94ED60@sarenet.es> <20091214154750.GF1666@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091214154750.GF1666@garage.freebsd.pl> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: zfs receive gives: internal error: Argument list too long X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 18:46:40 -0000 On Mon, Dec 14, 2009 at 04:47:50PM +0100, Pawel Jakub Dawidek wrote: > On Tue, Nov 03, 2009 at 12:08:54PM +0100, Borja Marcos wrote: > > > > On Oct 29, 2009, at 9:51 PM, Pawel Jakub Dawidek wrote: > > > > >On Wed, Oct 28, 2009 at 09:51:46PM +0100, Ronald Klop wrote: > > >>Hi, > > >> > > >>I'm forwarding this, because there was no answer on freebsd-stable. > > >> > > >>Does anybody know about this and have some tips on how to solve it? > > > > > >Could you try this patch: > > > > > > http://people.freebsd.org/~pjd/patches/zfs_recv_E2BIG.patch > > > > It's caused a panic for me on 8.0-RC2/amd64. Seems a new problem, > > never saw a panic in this situation before. > > > > How to reproduce: With /usr/src and /usr/obj in a dataset, just > > > > cd /usr/src > > make clean > > > > Instant panic, in less than 20 seconds. > > > > Trying to get panic information, unfortunately I'm running on VMWare > > Fussion and the silly thing doesn't offer the equivalent of a serial > > console. > > Martin, this is the panic report I was refering to. Could you please try > to reproduce it? Maybe first with my patch to confirm it is reproducible > and then with your patch to confirm it has no such problem? > I'd be very grateful if you could do that. I don't want something to go > into the tree if there might be a problem with the patch. > To add another report, I've been running your patch on one machine since late October/early November, and just installed another one with it a week ago. I haven't gotten any panics on either. I just did a make clean && make buildworld && make buildkernel && make clean (and ran the final make clean 9 times for good measure) on the second machine to try to reproduce the reported panic, but it worked fine. Both machines are running FreeBSD 8.0-STABLE/amd64 with ZFS from -CURRENT as of Dec 4, plus your patch. This patch is essentially mandatory for me to be able to run ZFS, since otherwise I can't backup my ZFS pools... - Pete Curry