From owner-freebsd-current Sat Feb 28 02:25:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21307 for freebsd-current-outgoing; Sat, 28 Feb 1998 02:25:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21276 for ; Sat, 28 Feb 1998 02:25:45 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id DAA28622; Sat, 28 Feb 1998 03:25:36 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd028615; Sat Feb 28 03:25:35 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id DAA10560; Sat, 28 Feb 1998 03:25:31 -0700 (MST) From: Terry Lambert Message-Id: <199802281025.DAA10560@usr08.primenet.com> Subject: Re: VM: Process hangs sleeping on vmpfw To: root@mantar.slip.netcom.com (Manfred Antar) Date: Sat, 28 Feb 1998 10:25:31 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Manfred Antar" at Feb 28, 98 00:21:23 am X-Mailer: ELM [version 2.4 PL25] 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 > > > > 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. > > I've got NFS FFS MFS MSDOS CD9660 PROCFS compiled in kernel everything is > mounted local on 1 4.3gig scsi drive: > /dev/sd0a on / > /dev/sd0s1e /var > /dev/sd0s1f /usr > > I don't use any LKM's and did a make world today at noon with current > as of then. I only saw the message once last night repeated 3 time on > xterm console.I have not noticed any problems This shows that you did not have anything other than FFS mounted. The warning can not occur with FFS. What this means is that the vnode pager was called to read in or write out pages on an FS that doesn't have a VOP_{GET|PUT}PAGES, and didn't have the legacy code referenced via stub functions. In simple terms, this means: (1) You had something other than an FFS filesystem mounted, and you aren't telling us about it. If you tell us about it, it's a simple fix (less than a minute). (2) Something is erroneously attempting a paging operation using an erroneous FS type. This is more serious, in that it means we are now catching some very bad behaviour that we didn't know about before. This is more complicated, because according to what we know about FreeBSD, you aren't supposed to need to do paging on an FS type that's not being used. It means that someone, somewhare, is probably stomping on a vnode's operations vector. We would need to change the warning to a panic, wait for you to repeat the problem, and then post-mortem the system dump to get things like a stack trace. I'm betting it's #1, though... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message