From owner-freebsd-hackers Sun May 31 10:59:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21950 for freebsd-hackers-outgoing; Sun, 31 May 1998 10:59:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21786 for ; Sun, 31 May 1998 10:58:27 -0700 (PDT) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id TAA17903; Sun, 31 May 1998 19:58:18 +0200 (MET DST) Message-Id: <199805311758.TAA17903@pat.idi.ntnu.no> To: xcejka00@dcse.fee.vutbr.cz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: nullfs problem In-Reply-To: Your message of "Sun, 31 May 1998 10:32:39 +0200 (MET DST)" References: <199805310832.IAA14045@sts.dcse.fee.vutbr.cz> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 31 May 1998 19:58:17 +0200 From: Tor Egge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anybody use nullfs layer? Is this only my problem on my box? > (Problem occurs if nullfs is mounted on root ffs.) Yes. On a production system running -current. Unfortunately I'm using the wrong set of patches. The unmodified nullfs layer in -current is broken for several reasons and should not be used. Fixing it correctly probably requires some changes to the VFS/VM subsystems (modifying vm_fault, resolving some locking issues and killing the buffer cache). - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message