Date: Fri, 27 Feb 1998 23:57:14 -0800 (PST) From: Manfred Antar <root@mantar.slip.netcom.com> To: Terry Lambert <tlambert@primenet.com> Cc: current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw Message-ID: <Pine.BSF.3.96.980227235452.4778A-100000@mantar.slip.netcom.com> In-Reply-To: <199802280754.XAA04775@mantar.slip.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Feb 1998, Terry Lambert wrote:
> > The machine is still running, though I can take a dump if anybody
> > (John?) wants to look at it. This is running a -CURRENT supped about
> > a week ago. Here's the ID of vm_fault.c:
> >
> > * $Id: vm_fault.c,v 1.80 1998/02/09 06:11:23 eivind Exp $
> >
> > If anybody wants access to the system, please let me know. Otherwise
> > I'll take it down some time tomorrow and take a dump.
>
> Check your dmesg/messages log for the following message:
>
> vnode_pager: *** WARNING *** stale FS code in system.
>
> If you have gotten this message, it means that you are trying to page
> out to an FS that has stale code (ie: a local media FS that does not
> support VOP_PUTPAGES). The FS needs corrected, so if you can identify
> which one it is, I can do a patch for you (it's pretty easy to make
> a VOP_{GET|PUT}PAGES to use the legacy code, but it must be explicitly
> used; doing this will [later] enable user space FS module developement
> to be stacked on top. The reason it's later is that there are still
> 151 imports for a non-stacking FS; the DDI/DKI for FS's needs a lot
> of cleanup to get it to the point that it can be proxied to user space).
>
I got that message on console last night and rebooted
did fsck and have not seen it lately. do i need to do anything ?
Thanks
Manfred
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?Pine.BSF.3.96.980227235452.4778A-100000>