On Mon, Aug 14, 2000 at 11:02:55AM -0700, Tom wrote:
> On Mon, 14 Aug 2000, Gary Kline wrote:
>
> >
> > Hi Folks,
> >
> > Over the weekend I discovered that my new 4.0 platform consistantly
> > fails to clean my SCSI drive #2 upon an improper shudown or even by
> > typing
> >
> > # fsck
> >
> > upon logging in as root and by-hand checking of the filesystems.
>
> 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*
successfully checks the root drive.
Any other FS or kernel wizards have a clue. I want to make this
experimental platform my main system while I build a real server.
gary
--
Gary D. Kline [EMAIL PROTECTED] Public service Unix
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
