Date: Mon, 14 Aug 2000 13:17:34 -0700 From: Gary Kline <kline@thought.org> To: Tom <tom@uniserve.com> Cc: Gary Kline <kline@thought.org>, freebsd-stable@FreeBSD.ORG Subject: Re: fack and /etc/fstab Message-ID: <20000814131734.A84069@tao.thought.org> In-Reply-To: <Pine.BSF.4.05.10008141222590.777-100000@shell.uniserve.ca>; from tom@uniserve.com on Mon, Aug 14, 2000 at 12:25:40PM -0700 References: <20000814121809.A83607@tao.thought.org> <Pine.BSF.4.05.10008141222590.777-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 14, 2000 at 12:25:40PM -0700, Tom wrote: > 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. > Given the exactly /dev/ from /etc/fstab, fsck will check that slice. But it will not check automatically if the machine crashes. It quits after fsck'ing /dev/da0*. This is what I don't understand. gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000814131734.A84069>