g_vfs_done error third part--PLEASE HELP!

Jeremy Chadwick koitsu at FreeBSD.org
Fri May 16 15:59:38 UTC 2008


On Fri, May 16, 2008 at 05:37:56PM +0200, Willy Offermans wrote:
> > > sun# fsck /dev/ar0s1g 
> > > ** /dev/ar0s1g
> > > ** Last Mounted on /share
> > > ** Phase 1 - Check Blocks and Sizes
> > > INCORRECT BLOCK COUNT I=34788357 (272 should be 264)
> > > CORRECT? [yn] y
> > > 
> > > INCORRECT BLOCK COUNT I=34789217 (296 should be 288)
> > > CORRECT? [yn] y
> > > 
> > > ** 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? [yn] y
> > > 
> > > SUMMARY INFORMATION BAD
> > > SALVAGE? [yn] y
> > > 
> > > BLK(S) MISSING IN BIT MAPS
> > > SALVAGE? [yn] y
> > > 
> > > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253
> > > blocks, 0.0% fragmentation)
> > > 
> > > ***** FILE SYSTEM MARKED CLEAN *****
> > > 
> > > ***** FILE SYSTEM WAS MODIFIED *****
> > > 
> > > The usual stuff I would say.
> > 
> > How is this usual?.  It appears to me you did have some filesystem
> > corruption.
> 
> What kind of filesystem corruption and how to solve that?

That's difficult to answer, for a lot of reasons.

Your original post stated that you were seeing g_vfs_done errors on the
console, and you were worried about what they implied.  Then someone
asked you "have you fsck'd the filesystem?", and you hadn't.  Then you
did fsck it, and as can be seen above, the filesystem had errors.

When combined with your below comment, it's very difficult to figure out
what's going on with your system over there, or what information you're
not disclosing.

Additionally, kris@ has stated that it looks like you may have a hard
disk that's gone bad, and that's a strong possibility as well.  SMART
statistics of the drives in your RAID array would be useful.

> I see these messages frequently if a FreeBSD machine unexpectedly reboots. Not only on this 
> system but also on others. I never worried about it.

Are you saying the above errors experienced were caused by an unexpected
crash or reboot?  If so, the filesystem should have been automatically
fsck'd shortly (60-120 seconds) after getting a "login:" prompt on the
console.

Is your filesystem UFS2 with softupdates enabled?  If so, and the
automatic fsck didn't happen, then that's something separate to look
into -- it should happen automatically with softupdates enabled.

More importantly, though, would be the explanation for why your system
is crashing/rebooting/power-cycling.  Data corruption can happen in
those situations, especially the latter, but any form of non-clean
shutdown should induce a fsck on UFS2+softupdate filesystems.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |



More information about the freebsd-stable mailing list