From owner-freebsd-stable@FreeBSD.ORG Fri Jul 6 17:51:17 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A9C1106564A for ; Fri, 6 Jul 2012 17:51:17 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 495028FC0A for ; Fri, 6 Jul 2012 17:51:17 +0000 (UTC) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id q66HpFOx000560 ; Fri, 6 Jul 2012 19:51:16 +0200 (CEST) X-Ids: 164 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.14.3/8.14.3) with ESMTP id q66HpDl1037062; Fri, 6 Jul 2012 19:51:13 +0200 (CEST) (envelope-from arno@heho.snv.jussieu.fr) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.14.3/8.14.3/Submit) id q66HpCSn037055; Fri, 6 Jul 2012 19:51:12 +0200 (CEST) (envelope-from arno) To: Vincent Hoffman From: "Arno J. Klaassen" References: <4FF7055D.9000507@unsane.co.uk> Date: Fri, 06 Jul 2012 19:51:12 +0200 In-Reply-To: <4FF7055D.9000507@unsane.co.uk> (Vincent Hoffman's message of "Fri\, 06 Jul 2012 16\:33\:49 +0100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at jchkmail.jussieu.fr with ID 4FF72593.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4FF72593.003/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ Cc: freebsd-stable@freebsd.org Subject: Re: nfs-bug when server for 9-Stable becomes client as well ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2012 17:51:17 -0000 Vincent Hoffman writes: > On 06/07/2012 14:19, Arno J. Klaassen wrote: >> Hello, >> >> looks like I discouvered a probable bug in the nfs-code, very >> easy to reproduce in my setup : >> >> >> Machine-1 : Today's 9-stable, exporting /files (ufs) and /z2 (zfs) >> >> Machine-2 : 8-stable as of April the 10th exporting /raid1 >> >> On Machine-1 I mount /raid1 (rw,nfsv3,intr,tcp,rsize=32768,wsize=32768) >> and start a script on this mount looping something like : >> >> dd if=/dev/random of=BIG bs=1048576 count=${SIZE} >> cp -fp BIG BIG2 >> cmp -x BIG BIG2 >> >> I let this run for 24 hours (from time to time stressing Machine-1 with >> other scripts, including provoking heavy swapping), no problem at all. >> >> However, then I mount /z2 (rw,nfsv3,intr,tcp,rsize=32768,wsize=32768) >> on Machine-2, and *immediately* the above loop on Machine-1 fails : >> >> Copying file ...cp: BIG: Permission denied >> >> No console messages this time, last time I got >> >> kernel: nfs_getpages: error 13 >> kernel: vm_fault: pager read error, pid 87803 (cmp) >> >> on Machine-1. >> >> I repeated this scenario by replacing Machine-2 with a good old >> 6-4-stable one, same outcome. >> >> Please tell me what I could do to nail this down a bit more. > Its possible (although not definite) that you have hit the a mountd bug > as documented in PRs > > kern/131342 > kern/136865 especially kern/131342 looks similar and quite old; funny I never hit this before, I basically do the same tests since 'ages' on each new box. Could be that faster network/cpu unreveals some race condition; I notice as well that this server is the first (IIRC) who uses 3 different IRQs for network interrupts (em(4) Intel(R) PRO/1000). > I've recently asked on -CURRENT about this and had a patch to try from > Rick, I'm testing it now but it doesnt seem to fix it for me, just > improve it alothough I'm trying to get enough runs to be a valid sample. > (see > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=377627+0+archive/2012/freebsd-current/20120701.freebsd-current > ) > > What I did for my production nas was edit mount.c so it didnt send a > SIGHUP to mountd as suggested by rick, as it was easy to do and non > intrusive. hmm, this means I should patch each fbsd-client, no? May be easier to patch mountd to ignore SIHGUP and use some non-standard signal to force re-init? Arno > Vince > >> >> Thanx in advance, >> >> Best, Arno >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"