From owner-freebsd-stable Thu Feb 18 17:43:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aniwa.sky (p9-max8.wlg.ihug.co.nz [209.79.142.201]) by hub.freebsd.org (Postfix) with ESMTP id 513171155F for ; Thu, 18 Feb 1999 17:38:16 -0800 (PST) (envelope-from andrew@squiz.co.nz) Received: from aniwa.sky (localhost [127.0.0.1]) by aniwa.sky (8.9.1a/8.9.1) with ESMTP id BAA24566 for ; Fri, 19 Feb 1999 01:38:13 GMT Message-Id: <199902190138.BAA24566@aniwa.sky> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-stable@FreeBSD.ORG Subject: Re: no dirty bufs panics any more... In-reply-to: Your message of "Thu, 18 Feb 1999 12:48:20 -0800." <199902182048.MAA14808@passer.osg.gov.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Feb 1999 14:38:13 +1300 From: Andrew McNaughton Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > since I stopped using an MFS as /tmp on the server, the `dirty bufs' > > > panics on server shutdown went away. Should this give us a strong > > > hint where to look for the errnous code? > > > > Hmmmm.... I'm getting this, too: > > > > syncing disks... 3 done > > panic: vinvalbuf: dirty bufs > > Automatic reboot in 15 seconds - press a key on the console to abort Is this something really simple like the mount_mfs process getting killed by shutdown before the buffers get flushed? The kernel gets pretty unhappy with file-systems disappearing when it's not ready for it. I've caused a kernel panic by removing a floppy without a umount. Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message