From owner-freebsd-current Mon Mar 25 04:27:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA20405 for current-outgoing; Mon, 25 Mar 1996 04:27:48 -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 EAA20374 for ; Mon, 25 Mar 1996 04:27:16 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id MAA02695; Mon, 25 Mar 1996 12:25:38 GMT From: Adam David Message-Id: <199603251225.MAA02695@veda.is> Subject: Re: async mounts, etc. To: hsu@clinet.fi (Heikki Suonsivu) Date: Mon, 25 Mar 1996 12:25:38 +0000 (GMT) Cc: freebsd-current@freebsd.org In-Reply-To: <199603250430.GAA21047@cantina.clinet.fi> from Heikki Suonsivu at "Mar 25, 96 06:30:08 am" 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 > From: Adam David > 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. > > Run fsck several times in row, running once may not be enough. If you run > into directories which are "corrupted" and fsck keeps cleaning and > salvaging them endlessly, clri the offending directory and salvage the > files from lost+found. > > The "endless fsck" problem is not specific to async mouts, but async mounts > naturally increase the amount of damage. > > -- > Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi > mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121 > The second run through fsck showed no further damage, and later "bad dir" panics involved directories that were not part of the previous damage. Something is broken, whether from a race condition or some other kind of size/load limit. -- Adam David