From owner-freebsd-current@FreeBSD.ORG Thu Feb 3 23:07:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3284216A4CE for ; Thu, 3 Feb 2005 23:07:32 +0000 (GMT) Received: from av3-2-sn3.vrr.skanova.net (av3-2-sn3.vrr.skanova.net [81.228.9.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB46443D55 for ; Thu, 3 Feb 2005 23:07:31 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av3-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 9174837E62; Fri, 4 Feb 2005 00:07:30 +0100 (CET) Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net [81.228.9.177]) by av3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 80B2937E57; Fri, 4 Feb 2005 00:07:30 +0100 (CET) Received: from sentinel (h205n1fls11o822.telia.com [213.64.66.205]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 59D1538011; Fri, 4 Feb 2005 00:07:30 +0100 (CET) From: "Daniel Eriksson" To: "'Mohan Srinivasan'" , "'Kris Kennaway'" Date: Fri, 4 Feb 2005 00:07:23 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20050203182917.40592.qmail@web80603.mail.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcUKLyRg2HbgDit7RMSyBQm/lkcvLQAFG5Eg cc: current@freebsd.org Subject: RE: Processes stuck in nfsreq X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 23:07:32 -0000 Mohan Srinivasan wrote: > Also, after you force a core, can you also try a quick > workaround - someone > else also reported NFS client hangs and said that things were fine > after they set mpsafenet to 0. It would be good to see if there's a > correlation there. That would be me. Unfortunately I've been busy with other things so I haven't had time to switch back to mpsafenet=1 and get you a dump. Since switching to mpsafenet=0 I haven't had a single NFS lock-up, so there seems to be a correlation. I have observed another strange thing lately. It seems like I keep getting file corruption when transferring large files (10-75MB each) over NFS with net.isr.enable=1. This is on an SMP client and a UP server, both running very recent 6-CURRENT kernels hooked up using a crossover cable (if_em on client, if_vr on server). The failure rate seems to be around 1 in 150 files or something like that, and the error shows up as a file that is a few hundred bytes shorter than the original (always resulting in a filesize on an 8kB boundary). I only switched off net.isr yesterday, so I still don't know for sure if it has cured the problem, but I've moved well over 1000 files since then without any corruption issues. Again, the amount of details I can provide is very limited. Sorry about that! /Daniel Eriksson