Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 01 Jul 1999 04:52:36 -0600
From:      Christopher Taylor <chris@thedial.com>
To:        Jorge Biquez <jbiquez@icsmx.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: hard disk Corrupted?
Message-ID:  <377B4874.53CB0AB1@thedial.com>
References:  <3.0.6.32.19990630135226.00c47560@intranet.com.mx>

next in thread | previous in thread | raw e-mail | index | archive | help
Jorge Biquez wrote:

> Hello all.
>
> I just installed version 3.1 . It is running fine.
> I had a problem with the no break connected to that machine and the machine
> wents down when the energy fail. The system restarted without trouble and I
> run a FSCK
> This is what I receive as report:
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 80764 files, 612372 used, 2906576 free (35416 frags, 358895 blocks, 1.0%
> fragmen
> tation)
>
> ============================================================
> ***** FILE SYSTEM STILL DIRTY *****
>
> ***** PLEASE RERUN FSCK *****
> ** /dev/rwd0s1e
> ** Last Mounted on /var
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 381 files, 3211 used, 26540 free (52 frags, 3311 blocks, 0.2% fragmentation)
>
> ***** FILE SYSTEM STILL DIRTY *****
>
> ***** PLEASE RERUN FSCK *****
>

This is probably happening because you are running 'fsck' on a mounted file
system. I recently found out that this is a very bad idea, after 'fsck' royally
messed up my file system. Remeber to 'umount' the filesystem before running
'fsck'.

--Chris



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?377B4874.53CB0AB1>