From owner-freebsd-current Sat Feb 28 00:12:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11171 for freebsd-current-outgoing; Sat, 28 Feb 1998 00:12:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11161 for ; Sat, 28 Feb 1998 00:12:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id AAA01283; Sat, 28 Feb 1998 00:09:59 -0800 (PST) Message-Id: <199802280809.AAA01283@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Manfred Antar cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-reply-to: Your message of "Fri, 27 Feb 1998 23:57:14 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Feb 1998 00:09:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Check your dmesg/messages log for the following message: > > > > vnode_pager: *** WARNING *** stale FS code in system. ... > I got that message on console last night and rebooted > did fsck and have not seen it lately. do i need to do anything ? It would help to know what filesystems you're running, and whether you are using any LKMs. Do you rebuild your LKMs when you update your kernel? The message indicates a potentially dangerous incompatability between one or more filesystems and other parts of the kernel. If this is due to oversight on our part, we would very much like to know so that it can be remedied ASAP. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message