From owner-freebsd-current Fri Oct 6 04:51:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA25461 for current-outgoing; Fri, 6 Oct 1995 04:51:18 -0700 Received: from veda.is (root@veda.is [193.4.230.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA25450 for ; Fri, 6 Oct 1995 04:51:14 -0700 Received: (from adam@localhost) by veda.is (8.6.12/8.6.12) id LAA02388 for freebsd-current@freefall.freebsd.org; Fri, 6 Oct 1995 11:51:06 GMT From: Adam David Message-Id: <199510061151.LAA02388@veda.is> Subject: nullfs problem? To: freebsd-current@freefall.freebsd.org Date: Fri, 6 Oct 1995 11:51:05 +0000 (GMT) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 468 Sender: owner-current@FreeBSD.org Precedence: bulk Is nullfs currently broken? I've been trying to use nullfs to union mount some directories over each other and it triggers spontaneous reboots within a few minutes of actual activity. Here's the sequence of mounts I've been using: mount -o union -t null tier1 basedir mount -o union -t null tier2 basedir tier1 contains pre-existing directories and tier2 contains files, which are all to be presented within a single common directory. -- Adam David