From owner-freebsd-stable Thu Jan 24 1: 0:30 2002 Delivered-To: freebsd-stable@freebsd.org Received: from eve.framatome.fr (eve.framatome.fr [195.101.50.66]) by hub.freebsd.org (Postfix) with ESMTP id 9CDBF37B41B for ; Thu, 24 Jan 2002 01:00:13 -0800 (PST) Received: from localhost (ubc@localhost) by eve.framatome.fr (8.11.3/8.11.2) with ESMTP id g0NFaKH66444 for ; Wed, 23 Jan 2002 16:36:20 +0100 (CET) (envelope-from ubc@eve.framatome.fr) Date: Wed, 23 Jan 2002 16:36:20 +0100 (CET) From: Claude Buisson To: Subject: NFS / softupdates problems Message-ID: <20020123154602.K66257-100000@eve.framatome.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am I the only one to have problems with NFS and/or softupdates ? For more than one year I upgraded a laptop running -stable as a NFS client (make installkernel,installworld) from a desktop where I make the world and the kernel. On these systems, / and /usr do not have softupdates enabled, but /usr/obj, /usr/src and /usr/ports are symlinked to /home where softupdates are enabled. The last time it worked was with sources cvsuped on December 13, on which I applied the "NFS-patches" from the hackers mailing list which were published on Daemon News the same day. (To prevent any remark, I never cvsup against my "running" source, but always against a clean base - and I always rm -rf obj) My next try was with clean source cvsuped on December 28, where the install was OK but where I got kernel panics on the NFS client when doing cp -R for src and ports. The panic message was (is): /kernel: panic: vinvalbuf: dirty bufs Same problem with source cvsuped on January 4 and 11. I tried different mount options, tried other servers at various (older) -stable levels, always with the same result. Then, I disabled softupdates on /home and found that I could copy the ports collection without any problem - with a performance drop. Using cvsweb, I found that for -current sys/ufs/ffs/ffs_softdep.c has been modified on January 11 (from 1.102 to 1.103) with a reference to my panic message in the log. I took the chance to (blindly) apply the patch to my -stable, and found that it seemed to solve my problem. As the log said "MFC after: 1 week", I thought I just had to wait a few days. But the source cvsuped on January 19 gave the same panic without the ffs_softdep.c patch on a system with softupdates enabled, and no panic with softupdates disabled. With the ffs-softdep.c patched, I got errors: Input/output error and Permission denied when copying the ports collection, which were not repeated on a second try. So, is this problem specific to my systems ? can somebody help ? what can/must I do to help elucidate it ? Claude Buisson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message