From owner-freebsd-current Mon Jun 8 11:33:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12771 for freebsd-current-outgoing; Mon, 8 Jun 1998 11:33:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12596 for ; Mon, 8 Jun 1998 11:32:33 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA26954; Mon, 8 Jun 1998 11:32:23 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd026913; Mon Jun 8 11:32:17 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA12771; Mon, 8 Jun 1998 11:32:16 -0700 (MST) From: Terry Lambert Message-Id: <199806081832.LAA12771@usr04.primenet.com> Subject: Re: NFS / softupdates interaction problems? To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 8 Jun 1998 18:32:16 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199806081336.JAA06735@grasshopper.cs.duke.edu> from "Andrew Gallatin" at Jun 8, 98 09:36:38 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Under heavy write load, the FreeBSD-current NFS server complains > repeatedly of problems like the following: > > ffs_fsync: dirty: f749a880: type VREG, usecount 1, writecount 0, refcount 1023, flags (VOBJBUF) > tag VT_UFS, ino 7937, on dev 21, 2 lock type inode: EXCL (count 1) by pid 293 > > (pid 293 is an nfsd). > > These messages stop if I turn off softupdates, or if I set > vfs.nfs.async=1 (or, obviously, if I compile w/o DIAGNOSTIC). This > only happens with remote writes, local writes do not trigger this > case. > > > Occasionally I'll get a crash like the following. I've seen this > stacktrace on -current, so I guess its a known problem. [ ... ] > Cannot access memory at address 0x1c5e10bb. I am unclear here, so I suspect others are as well. Does the crash still occur regarless of your soft updates/vfs.nfs.async settings, or is the crash cured by the same cases where the messages are cured? Ie: is the crash a soft updates problem or an general problem? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message