From owner-freebsd-hackers Sun Oct 6 11:45:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04312 for hackers-outgoing; Sun, 6 Oct 1996 11:45:48 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA04307 for ; Sun, 6 Oct 1996 11:45:45 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id NAA00253; Sun, 6 Oct 1996 13:45:06 -0500 (EST) From: "John S. Dyson" Message-Id: <199610061845.NAA00253@dyson.iquest.net> Subject: Re: nullfs: Panicing... To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 6 Oct 1996 13:45:06 -0500 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199610060925.LAA06403@keltia.freenix.fr> from "Ollivier Robert" at Oct 6, 96 11:25:30 am Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > According to Joao Carlos Mendes Luis: > > approach was to use nullfs, but everytime I try to edit (vi) > > a file in the nullfs mounted directory, the system panics. Everything > > else works (or seens to work) ok. > > > Is this already known ? > > Yes.Some of the special filesystems are broken since we got an unified > VM/buffer cache (just after FreeBSD 2.0). John said he will fix them for > 2.2. > I hope to fix them, but the ~hsu VFS stuff needs to be committed. I am working on LFS (with a practically complete re-do for efficiency.) John