File System errors

[Jerry McAllister]

On Tue, May 15, 2007 at 12:15:06PM -0600, Ross Penner wrote:

> I recently had my system freeze so I had to manually restart it. I was
> worried that there would be some problems with the filesystem so I
> looked into the matter and discovered the utility fsck. I ran this as
> root and I got the following:
> 
> rosbot# fsck
> ** /dev/ar0s1a (NO WRITE)
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 1549 files, 27349 used, 226466 free (650 frags, 28227 blocks, 0.3%
> fragmentation)
> ** /dev/ar0s1e (NO WRITE)
> ** Last Mounted on /tmp
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 39 files, 2445 used, 251370 free (50 frags, 31415 blocks, 0.0% 
> fragmentation)
> ** /dev/ar0s1f (NO WRITE)
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> FREE BLK COUNT(S) WRONG IN SUPERBLK
> SALVAGE? no
> 
> 292882 files, 98192697 used, 135895442 free (39610 frags, 16981979
> blocks, 0.0% fragmentation)
> ** /dev/ar0s1d (NO WRITE)
> ** Last Mounted on /var
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> UNREF FILE I=117781  OWNER=root MODE=140666
> SIZE=0 MTIME=May 15 09:56 2007
> CLEAR? no
> 
> UNREF FILE I=141337  OWNER=teamspeak MODE=100600
> SIZE=2048 MTIME=May 15 09:56 2007
> CLEAR? no
> 
> ** Phase 5 - Check Cyl groups
> FREE BLK COUNT(S) WRONG IN SUPERBLK
> SALVAGE? no
> 
> SUMMARY INFORMATION BAD
> SALVAGE? no
> 
> 18514 files, 70825 used, 905728 free (6688 frags, 112380 blocks, 0.7%
> fragmentation)
> 
> 
> It seems to my unexperienced eye that their are problems in some of
> the filesystems, but they arn't being resolved. I tried running fsck
> -y  and nothing changed. What am I doing wrong? How can I resolve
> these issues? Thanks for any help you can offer.

I may be mistaking something, but it kind of looks like it doesn't
have write access to the drive.    Fsck has to be able to write to
fix anything.    

Also, you need to answer 'y' when it asks to 'salvage'.  Of course, 
doing the fsck -y should take care of that issue, but it still must
have write permission.   I don't know why it wouldn't have write ability.

////jerry

> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"