From owner-freebsd-stable@FreeBSD.ORG Mon Feb 27 15:36:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C046116A422 for ; Mon, 27 Feb 2006 15:36:22 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34D7E43D5A for ; Mon, 27 Feb 2006 15:36:12 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k1RFaBdY027850; Mon, 27 Feb 2006 10:36:11 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id k1RFaAJx093179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2006 10:36:11 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060227102902.08d08268@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 27 Feb 2006 10:35:24 -0500 To: Danny Butroyd From: Mike Tancsa In-Reply-To: <44031A0E.9060402@g-mapps.com> References: <4402F009.1000407@g-mapps.com> <6.2.3.4.0.20060227093542.086c56c0@64.7.153.2> <44031194.8000300@g-mapps.com> <6.2.3.4.0.20060227095704.085300c8@64.7.153.2> <44031A0E.9060402@g-mapps.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: freebsd-stable@freebsd.org Subject: Re: nfs woes in FreeBSD 6.0 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: Mon, 27 Feb 2006 15:36:23 -0000 At 10:26 AM 27/02/2006, Danny Butroyd wrote: >OK, do the changes affect both server and client and is there any >documentation on the changes? cvs commits and reading this mailing is the best place to track what has changed in detail. Unfortunately, there is no middle ground source for information. I use a procmail script to sort all RELENG_6 commits into a file that I can then search through after the fact. The descriptions generally offer an OK description as to what was changed / fixed improved. If that fails, going back to the original commit message might offer more detail. e.g. a quick perusal of just the nfs code commits shows a couple of obvious bug fixes. maxim 2005-12-15 18:10:37 UTC FreeBSD src repository Modified files: (Branch: RELENG_6) sys/nfsclient nfs_socket.c Log: MFC rev. 1.134: fix for a bug where NFS/TCP would not reconnect (in the case where the server FIN'ed). PR: kern/88833 Requested by: Roman V. Palagin Approved by: Mohan Strinivasan Revision Changes Path 1.125.2.5 +1 -1 src/sys/nfsclient/nfs_socket.c tegge 2006-01-14 01:05:22 UTC FreeBSD src repository Modified files: (Branch: RELENG_6) sys/nfs4client nfs4_vfsops.c Log: MFC: Obtain mount point lock before restarting sync loop if vget() failed. Revision Changes Path 1.20.2.1 +1 -0 src/sys/nfs4client/nfs4_vfsops.c rwatson 2006-02-14 00:06:32 UTC FreeBSD src repository Modified files: (Branch: RELENG_6) sys/nfsclient nfs_lock.c Log: Merge nfs_lock.c:1.43 from HEAD to RELENG_6: In nfs_dolock(), GC now under-used ioflg, rendered obsolete when we moved from using a fifo to talk to rpc.lockd to using a special device node. Approved by: re (scottl) rees 2006-02-16 02:39:53 UTC FreeBSD src repository Modified files: (Branch: RELENG_6) sys/nfsclient nfs_socket.c Log: MFC rev 1.135: Don't log an error on tcp connection reset, even if we don't get ECONNRESET. Submitted by: cel@citi.umich.edu Approved by: re (scottl) Revision Changes Path 1.125.2.6 +2 -2 src/sys/nfsclient/nfs_socket.c > > > > BTW, if you are using tcp mounts, and you have devices not on the same > > subnet, setting > > net.inet.tcp.inflight.enable=0 > > helps with performance. However, this is a separate issue to the > > problems you are seeing. > > >Yeah, I saw this in the list archives :) > >Danny > > ---Mike > > > > > >> Danny > > > > _______________________________________________ > > 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" > >