Thanks to:
1) Tom Blinn
2) alan_at_nabeth.cxo.dec.com
3) Grant Van Dyck
The Solution:
1) Really it's not a problem, not is possible to run fsck
when the file system is mounted, this is the cause of the "problem".
Then first step, umount the file system.
2) To force to the command fsck to check a file system: fsck
-o -y /usr.
The orifinal question:
> Hi friends:
>
> I have a Alpha 4000 runing Unix 4.0E, when I execute fsck -n
> /usr, I obtain the following message:
>
> *** begin of box message
>
> ** /dev/rre0g (NO WRITE)
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> INCORRECT BLOCK COUNT I=345695 (288 should be 208)
> CORRECT? no
>
> INCORRECT BLOCK COUNT I=345787 (880 should be 208)
> CORRECT? no
>
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> UNREF FILE I=291913 OWNER=root MODE=100644
> SIZE=4 MTIME=Aug 19 07:44 1999
> CLEAR? no
>
> UNREF FILE I=345733 OWNER=dloyola MODE=100600
> SIZE=0 MTIME=Aug 19 09:43 1999
> RECONNECT? no
>
> CLEAR? no
>
> ** Phase 5 - Check Cyl groups
> BLK(S) MISSING IN BIT MAPS
> SALVAGE? no
>
> SUMMARY INFORMATION BAD
> SALVAGE? no
>
> FREE BLK COUNT(S) WRONG IN SUPERBLK
> SALVAGE? no
>
> 27230 files, 1773731 used, 1196408 free (3240 frags, 149146 blocks,
0.1%
> fragmentation)
> /sbin/ufs_fsck -n /usr
>
> *** end of box message
>
> I shutdown the box, boot at single user, then I ran, fsck -y /usr,
> the box said: fsck don't required, ufs unmounted clearly. But when,
> restore the entire system, again the fsck command mark the same
> problems.
Again Thanks
Edgar Barrera
Received on Fri Aug 20 1999 - 17:31:52 NZST