From owner-freebsd-current Sat Feb 28 07:21:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17337 for freebsd-current-outgoing; Sat, 28 Feb 1998 07:21:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17332 for ; Sat, 28 Feb 1998 07:21:30 -0800 (PST) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([208.133.153.147]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA40; Sat, 28 Feb 1998 10:17:56 -0500 Received: (from root@localhost) by rhiannon.scsn.net (8.8.8/8.8.7) id KAA00816; Sat, 28 Feb 1998 10:21:54 -0500 (EST) (envelope-from root) Message-ID: <19980228102154.10781@scsn.net> Date: Sat, 28 Feb 1998 10:21:54 -0500 From: dmaddox@scsn.net (Donald J. Maddox) To: Terry Lambert Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw Reply-To: dmaddox@scsn.net Mail-Followup-To: Terry Lambert , FreeBSD-current@FreeBSD.ORG References: <19980228155309.44211@freebie.lemis.com> <199802280623.XAA21476@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802280623.XAA21476@usr05.primenet.com>; from Terry Lambert on Sat, Feb 28, 1998 at 06:23:38AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 28, 1998 at 06:23:38AM +0000, Terry Lambert wrote: > 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'm getting this when accessing ext2fs filesystems... It looks like ext2fs is broken in more ways than one, but I thought you might like to know about this one :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message