From owner-freebsd-current Sat Mar 23 18:48:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA20148 for current-outgoing; Sat, 23 Mar 1996 18:48:30 -0800 (PST) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA20143 for ; Sat, 23 Mar 1996 18:48:23 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id CAA00668 for freebsd-current@freebsd.org; Sun, 24 Mar 1996 02:48:08 GMT From: Adam David Message-Id: <199603240248.CAA00668@veda.is> Subject: async mounts, etc. To: freebsd-current@freebsd.org Date: Sun, 24 Mar 1996 02:48:07 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL13 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been using an async mount for a newsspool for a few months, but today it seems that some limit was exceeded and it panicked on average twice an hour with "bad dir". It did not help to let fsck exercise the disk - I mean that repair to the filesystem claimed to be successful but there were further panics. After mounting without the async option, the filesystem is stable again. I have a crashdump, but I suspect it only shows that the filesystem was damaged. This reminds me of another similar problem with an NFS mounted from localhost with the union option, it happened a few months back. After many weeks of regular operation, it crashed when some limit was exceeded. After this, every attempt to mount the upper layer would cause an instant panic. There was not enough diskspace at the time to take a crashdump, and I have not dared test it since. I used a bunch of symbolic links in the end, instead of the lower layer. Oh, and that reminds me to ask: Just how broken is nullfs? Is it lying broken because it depends on other stuff not yet settled, or is it just waiting to be fixed? In the preceding description, I said "exceeded some limit" because all of a sudden with no obvious explanation (for instance due to kernel changes, etc), a system which was working reliably and was to all intents and purposes normal, suddenly became unstable. The NFS.union directory contained several thousand entries at the time. -- Adam David