From owner-freebsd-current Thu Sep 12 5:54:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5B6937B400; Thu, 12 Sep 2002 05:54:54 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 852FB43E4A; Thu, 12 Sep 2002 05:54:53 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA04642; Thu, 12 Sep 2002 22:54:51 +1000 Date: Thu, 12 Sep 2002 22:59:23 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Panic during reboot in vflush() In-Reply-To: <3D8045D3.35A3DECE@FreeBSD.org> Message-ID: <20020912224638.V6305-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 12 Sep 2002, Maxim Sobolev wrote: > Any ideas? See the thread about "Page faults from bento cluster (Re: Problems reading vmcores)]" which seemed to diagnose this. The last mail that I got about this pointed to: http://www.chesapeake.net/~jroberson/VFSsmp.patch As a workaround, try unmounting most of your filesystems from userland using umount -A. Don't use umount -f. (There seems to be a problem with the MNT_FORCECLOSE case in vflush(). MNT_FORCECLOSE is set more than I thought: it is always set for the final unmount done by reboot(2)). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message