From owner-freebsd-stable Tue Jan 28 12:51:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA09234 for stable-outgoing; Tue, 28 Jan 1997 12:51:21 -0800 (PST) Received: from amazon.cs.umd.edu (amazon.cs.umd.edu [128.8.128.40]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09229; Tue, 28 Jan 1997 12:50:52 -0800 (PST) From: jlee@cs.umd.edu Received: by amazon.cs.umd.edu (8.8.4/UMIACS-0.9/04-05-88) id PAA01402; Tue, 28 Jan 1997 15:50:35 -0500 (EST) Message-Id: <199701282050.PAA01402@amazon.cs.umd.edu> Subject: Is "NULLFS" broken? To: FreeBSD-current@freebsd.org, FreeBSD-stable@freebsd.org Date: Tue, 28 Jan 1997 15:50:34 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear FreeBSDers: I noticed that whenever I have "null" mounted file systems, I get kernel page faults sometime later. The system without mounted NULLFS doesn't generate kernel page faults as far as I can tell. I am running FreeBSD-2.2/ctm/src-2.2.0139.gz and doing a lot of reading and writing to the "null" mounted directory as root. I tried FreeBSD-2.1.6.1 and I still got kernel page faults with NULLFS mounted. I am a happy user of FreeBSD for a year now. I would be a happier user if I don't get the kernel page faults with NULLFS. :-) Am I doing something stupid or the "null fs" is broken? Please help me solving this problem. Thank you in advance. jlee@cs.umd.edu