From owner-freebsd-current Sun Mar 29 22:38:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26603 for freebsd-current-outgoing; Sun, 29 Mar 1998 22:38:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26598 for ; Sun, 29 Mar 1998 22:38:10 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA09465; Mon, 30 Mar 1998 01:38:01 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803300638.BAA09465@dyson.iquest.net> Subject: Re: panic: "vm_fault: fault on nofault entry" with softupdates In-Reply-To: <199803300400.UAA05599@rah.star-gate.com> from Amancio Hasty at "Mar 29, 98 08:00:42 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Mon, 30 Mar 1998 01:38:01 -0500 (EST) Cc: rb@gid.co.uk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] 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 > This is an old soft update panic . Try John's latest check in: > > dyson 1998/03/29 10:23:45 PST > > Modified files: > sys/kern vfs_syscalls.c > Log: > Correct a significant problem with the softupdates port. Allow fsync > to work properly within the softupdates framework, and thereby eliminate > some unfortunate panics. > > Revision Changes Path > 1.96 +11 -4 src/sys/kern/vfs_syscalls.c > > -------- > > Hope that my testing goes well over here . Usually, I can crash the system > within an hour if I enable soft updates. > PS. I didn't fix anything other than add more facets to the port of the code. Now, the system seems as reliable as it was before the vtruncbuf change, but there is absolutely no reason other than fsync not working why the addition of vtruncbuf caused problems. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message