From owner-freebsd-current Sat Feb 28 10:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01240 for freebsd-current-outgoing; Sat, 28 Feb 1998 10:09:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01191 for ; Sat, 28 Feb 1998 10:09:28 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id VAA00816; Sat, 28 Feb 1998 21:04:45 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id VAA02290; Sat, 28 Feb 1998 21:13:10 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802281813.VAA02290@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: FreeBSD-current@FreeBSD.ORG Subject: Re: VM: Process hangs sleeping on vmpfw In-reply-to: Your message of "Sat, 28 Feb 1998 06:23:38 GMT." <199802280623.XAA21476@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Feb 1998 21:13:09 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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). In fact, this mean that you are trying to _page in from_ FS that was recently broken (i.e. local media FS that does not support VOP_GETPAGES). vnode_pager_putpages does not check for EOPNOTSUPP. I thought it is job of the submitter/committer to find all places broken by the changes and fix them. Here is a (partial?) list of broken filesystems: NFS, CD9660, EXT2FS, MSDOSFS. > 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. Well, I don't know what do you need for user space FS module development, but I still believe that you introduced lot of unnecessary complexity. First, why default/standard/generic getpages/putpages routines does not have interface of VOP_GETPAGES/VOP_PUTPAGES vnode operations? It would be easier for a filesystem to just add some entries to their operations tables than also cut&paste implementation (even trivial) of these operations from ffs. Second, why don't put the operations to default_vnodeop_entries? It is used exactly by local media filesystems. Stacking layers use bypass routines instead (unionfs is an exception). So, filesystems even would not notice this change, until they really want their own implementation of getpages/putpages What is wrong in the above? I can send a patch for you... It is indeed pretty easy... Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message