From owner-freebsd-questions Mon Aug 30 11:32:57 1999 Delivered-To: freebsd-questions@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id E4BF8152F6 for ; Mon, 30 Aug 1999 11:32:49 -0700 (PDT) (envelope-from forrie@forrie.com) Received: from boomer (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id OAA28344 for ; Mon, 30 Aug 1999 14:31:12 -0400 (EDT) Message-Id: <4.2.0.58.19990830142749.00ac4ed0@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 30 Aug 1999 14:29:41 -0400 To: freebsd-questions@freebsd.org From: Forrest Aldrich Subject: FSCK information (follow-up) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Though I received no help in diagnosing the "dirty file system" problem (see my previous posting), the solution wasn't very obvious, and perhaps fsck (or some other mechanism) could have helped. In my case, I had listed the incorrect mount point for the same device. This caused a filesystem busy error. And for some reason the other filesystems were reported as dirty by fsck. Having a better error response (if possible) would have saved a lot of time. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message