From owner-freebsd-fs@FreeBSD.ORG Thu Jan 24 18:49:12 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3CDFD5F1 for ; Thu, 24 Jan 2013 18:49:12 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by mx1.freebsd.org (Postfix) with ESMTP id CFA8DE16 for ; Thu, 24 Jan 2013 18:49:11 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.12]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Lnmgj-1UfVqj2grn-00hyCf for ; Thu, 24 Jan 2013 19:49:10 +0100 Received: (qmail invoked by alias); 24 Jan 2013 18:49:10 -0000 Received: from cm56-168-232.liwest.at (EHLO bones.gusis.at) [86.56.168.232] by mail.gmx.net (mp012) with SMTP; 24 Jan 2013 19:49:10 +0100 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX183RQcrvRQ3lZC92BaP33z2miqhc45iF+iGlK6+oE Gu4laaVCN2Z+cV From: Christian Gusenbauer To: Konstantin Belousov Subject: Re: 9.1-stable crashes while copying data from a NFS mounted directory Date: Thu, 24 Jan 2013 19:50:49 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <201301241805.57623.c47g@gmx.at> <20130124180359.GH2522@kib.kiev.ua> <20130124180723.GI2522@kib.kiev.ua> In-Reply-To: <20130124180723.GI2522@kib.kiev.ua> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201301241950.49455.c47g@gmx.at> X-Y-GMX-Trusted: 0 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 18:49:12 -0000 On Thursday 24 January 2013 19:07:23 Konstantin Belousov wrote: > On Thu, Jan 24, 2013 at 08:03:59PM +0200, Konstantin Belousov wrote: > > On Thu, Jan 24, 2013 at 06:05:57PM +0100, Christian Gusenbauer wrote: > > > Hi! > > > > > > I'm using 9.1 stable svn revision 245605 and I get the panic below if I > > > execute the following commands (as single user): > > > > > > # swapon -a > > > # dumpon /dev/ada0s3b > > > # mount -u / > > > # ifconfig age0 inet 192.168.2.2 mtu 6144 up > > > # mount -t nfs -o rsize=32768 data:/multimedia /mnt > > > # cp /mnt/Movies/test/a.m2ts /tmp > > > > > > then the system panics almost immediately. I'll attach the stack trace. > > > > > > Note, that I'm using jumbo frames (6144 byte) on a 1Gbit network, maybe > > > that's the cause for the panic, because the bcopy (see stack frame > > > #15) fails. > > > > > > Any clues? > > > > I tried a similar operation with the nfs mount of rsize=32768 and mtu > > 6144, but the machine runs HEAD and em instead of age. I was unable to > > reproduce the panic on the copy of the 5GB file from nfs mount. Hmmm, I did a quick test. If I do not change the MTU, so just configuring age0 with # ifconfig age0 inet 192.168.2.2 up then I can copy all files from the mounted directory without any problems, too. So it's probably age0 related? Ciao, Christian.