Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Feb 2004 14:07:57 -0800
From:      "Sean Noonan" <snoonan@snoonan.com>
To:        <freebsd-questions@freebsd.org>
Subject:   Please help - URGENT - disk/fsck problems!
Message-ID:  <000001c3f4d9$5fdcc3d0$6706a8c0@FLOYD>

Next in thread | Raw E-Mail | Index | Archive | Help
I'm in need of urgent help.  I have a production 4.9-RELEASE server.  I
track STABLE, last cvsup/make world was about two months ago.  After
powering on after an extended power outage (was given advanced notice by
electric company and I shut the server down before the outage occurred), =
the
server hung with disk problems and suggested I run fsck.

I ran fsck and came up with thousands of errors.  I re-ran fsck and came =
up
with less.  I repeated this process for what seems like a hundred times. =
 No
matter what I do, though, I still have errors that fsck seems unable to
repair.  HELP!!
=20
What are my options?  Is there any way to repair the file system?  How,
exactly?  I backup every night with AMANDA to a DLT drive.  Would =
restoring
from tape also restore the errors to the file system?
=20
I'm desperate, if any one could assist I'd be very grateful!=20

TIA,=20

--Sean Noonan


P.S. - Here's the output from fsck (yes, I realize the volume is mounted =
in
this output and therefore the filesystem is read-only):

bash-2.05b# fsck
** /dev/da0s1a (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
2004 files, 38340 used, 90659 free (307 frags, 11294 blocks, 0.2%
fragmentation)

** /dev/da0s1f (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
10301 files, 26910 used, 231121 free (169 frags, 28869 blocks, 0.1%
fragmentation)

** /dev/da0s1g (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=3D447212 (5280 should be 4064)
CORRECT? no
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT FILE I=3D648323  OWNER=3Dman MODE=3D0
SIZE=3D0 MTIME=3DFeb 16 13:35 2004  COUNT 0 SHOULD BE -1
ADJUST? no
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
ALLOCATED FRAG 890704 MARKED FREE
ALLOCATED FRAG 890705 MARKED FREE
.
.
.
ALLOCATED FRAG 4937333 MARKED FREE
ALLOCATED FRAG 4937334 MARKED FREE
ALLOCATED FRAG 4937335 MARKED FREE
253019 files, 2151531 used, 3184970 free (57794 frags, 390897 blocks, =
1.1%
fragmentation)

** /dev/da0s1e (NO WRITE)
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=3D151455 (6912 should be 640)
CORRECT? no
INCORRECT BLOCK COUNT I=3D151456 (95008 should be 225856)
CORRECT? no
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity   =20
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
ALLOCATED FRAG 646592 MARKED FREE
ALLOCATED FRAG 646593 MARKED FREE
ALLOCATED FRAG 646594 MARKED FREE
.
.
.
ALLOCATED FRAG 679445 MARKED FREE
ALLOCATED FRAG 679446 MARKED FREE
ALLOCATED FRAG 679447 MARKED FREE
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
1760 files, 98086 used, 1997709 free (1317 frags, 249549 blocks, 0.1%
fragmentation)

bash-2.05b#



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?000001c3f4d9$5fdcc3d0$6706a8c0>