Date: Mon, 30 Mar 1998 01:38:01 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: hasty@rah.star-gate.com (Amancio Hasty) Cc: rb@gid.co.uk, current@FreeBSD.ORG Subject: Re: panic: "vm_fault: fault on nofault entry" with softupdates Message-ID: <199803300638.BAA09465@dyson.iquest.net> In-Reply-To: <199803300400.UAA05599@rah.star-gate.com> from Amancio Hasty at "Mar 29, 98 08:00:42 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803300638.BAA09465>