From owner-freebsd-stable Mon Aug 14 12:25:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id CF81737B5E6 for ; Mon, 14 Aug 2000 12:25:47 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 13OPrj-000J2j-00; Mon, 14 Aug 2000 12:25:43 -0700 Date: Mon, 14 Aug 2000 12:25:40 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Gary Kline Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fack and /etc/fstab In-Reply-To: <20000814121809.A83607@tao.thought.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Aug 2000, Gary Kline wrote: > > Unless you are running single user with all filesystems mounted > > read-only, fsck will consider all filesystems to be dirty, because they > > are active. Running fsck on an active filesystem is a really bad idea. > > > > You're right. I'm aware of the shouldn't-do's, Tom, but > thanks for the heads-up. In multi-user, fsck does a (NO-WRITE) > check. But it should see my 2nd drive. > > I forgot to mention that for unknown reasons > > # fsck /dev/da1* > > fails, while > > # fsck /dev/da0* Uhh, if those the exact commands you are entering, you are telling fsck to check a lot of nonexistant devices. /dev/ contains daX entries for each slice, which can't be fscked. You should use the exact device name for each filesystem you want to check, and everything will work. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message