help needed to fix Filesystem inconsistensy error

rashmi ns nsrashmi at gmail.com
Thu Oct 27 21:24:39 PDT 2005


Hello List,
As i were testing our kernel modules systems used to crash and reboot
ofently it you used to prompt that filesystem was inconsistent .then we ran
fsck_ffs /dev/ad0s1f and the filesystem was marked clean .When we did a
similar thing on the other drive which was also inconsistent we could not
fix the problem .
i ran fsck_ffs -b <alternative superblock /*( got from newfs -N
/dev/ad0s1d)*/ /dev/ad0s1d
even then the FS error persists
i would like to add the detials

dev/ad0s1a 253678 60678 172706 26% /
devfs 1 1 0 100% /dev
/dev/ad0s1e 253678 146 233238 0% /tmp
/dev/ad0s1f 7005174 2937826 3506936 46% /usr
/dev/ad0s1d 253678 83158 150226 36% /var
#umount -f /var
freedom# fsck /dev/ad0s1d
** /dev/ad0s1d
BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
ALTERNATE

LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y

32 is not a file system superblock
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).
freedom# newfs -N /dev/ad0s1d
/dev/ad0s1d: 256.0MB (524288 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 64.02MB, 4097 blks, 8256 inodes.
super-block backups (for fsck -b #) at:
160, 131264, 262368, 393472
freedom# fsck -b 160 /dev/ad0s1d
fsck: illegal option -- b
usage: fsck [-BFdfnpvy] [-T fstype:fsoptions] [-t fstype] [special|node]...
freedom# fsck_ffs -b 160 /dev/ad0s1d
Alternate super block location: 160
** /dev/ad0s1d
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
3229892416 BAD I=16520
UNEXPECTED SOFT UPDATE INCONSISTENCY

6710895 BAD I=16520
UNEXPECTED SOFT UPDATE INCONSISTENCY
.
.
.
4524867752423034432 BAD I=16520
UNEXPECTED SOFT UPDATE INCONSISTENCY

EXCESSIVE BAD BLKS I=16520
CONTINUE? [yn]y
-4571961484719087296 BAD I=16543
UNEXPECTED SOFT UPDATE INCONSISTENCY

-4571961484719087296 BAD I=16543
UNEXPECTED SOFT UPDATE INCONSISTENCY

.
.
8423031159521548 BAD I=17580
UNEXPECTED SOFT UPDATE INCONSISTENCY

EXCESSIVE BAD BLKS I=17580
CONTINUE? [yn] y
** Phase 2 - Check Pathnames
DIRECTORY CORRUPTED I=16814 OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:44 2005
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

SALVAGE? [yn]y
MISSING '.' I=16814 OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:44 2005
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn]y
IRECTORY CORRUPTED I=16816 OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:31 2005
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

SALVAGE? [yn] y
UNEXPECTED SOFT UPDATE INCONSISTENCY
I OUT OF RANGE I=731293
NAME=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

REMOVE? [yn]y
ISSING '..' I=16822 OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:33 2005
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY
CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS condvar.h

UNEXPECTED SOFT UPDATE INCONSISTENCY
fsck_ffs: inoinfo: inumber 731294 out of range
freedom# fsck /dev/ad0s1d
** /dev/ad0s1d
BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
ALTERNATE

LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y

32 is not a file system superblock
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).


Kindly tell me how can this be fixed / re-installation is the solution,
Thanks and regards,
rashmi.n.s


More information about the freebsd-questions mailing list