Re: strange df output

Maxim Maximov wrote:
> Hello.
>
>	Just noticed strange df output (/tmp):
>
> mcsi at ultra(ttyp1) [141] /# df -i
> Filesystem  1K-blocks    Used   Avail Capacity iused  ifree %iused 
> Mounted on
> /dev/ad2s3a    253678  116458  116926    50%    2574  30448    8%   /
> devfs               1       1       0   100%       0      0  100%   /dev
> /dev/ad2s3e    253678     -18  233402    -0%       8  33014    0%   /tmp
> ...

Same here. "fsck -y" does not seem to work. It always answers "no" to
all questions.  The "UNEXPECTED SOFT UPDATE INCONSISTENCY"s below do
not show up consistently (only about half the time)


##########
# uname -a
##########
FreeBSD *** 6.0-CURRENT FreeBSD 6.0-CURRENT #4: Fri Oct 22 16:19:31 JST 2004
     root_at_***:/usr/obj/usr/src/sys/GENERIC  amd64

#########
# df
#########
Filesystem  1K-blocks                Used                Avail Capacity  Mounted on
/dev/da0s1a    253678              116100               117284    50%    /
devfs               1                   1                    0   100%    /dev
/dev/da0s1d    253678               41320               192064    18%    /var
/dev/da0s1e    253678               11890               221494     5%    /tmp
/dev/da0s1f  12531178             9102814              2425870    79%    /usr
/dev/da1     17353432            13968972              1996186    87%    /shogidb
/dev/ad0s4d  37571788            31296822              3269224    91%    /shogidb2
/dev/ad0s4e  37098890 3208655351830810976 -3208655351796679996 9401005631338%    /shogidb3
procfs              4                   4                    0   100%    /proc


###########################
# tail /var/log/dmesg.today     
###########################
pid 64 (syncer), uid 0 inumber 54 on /shogidb3: bad block
bad block -7284700853228855270, ino 54
pid 64 (syncer), uid 0 inumber 54 on /shogidb3: bad block
bad block 4893737993591775445, ino 54
pid 64 (syncer), uid 0 inumber 54 on /shogidb3: bad block
bad block 51707012973938502, ino 54
pid 64 (syncer), uid 0 inumber 54 on /shogidb3: bad block
bad block 6666255807292474078, ino 54
pid 64 (syncer), uid 0 inumber 54 on /shogidb3: bad block
handle_workitem_freeblocks: block count


#################
# fsck /shogidb3   
#################
#** /dev/ad0s4e (NO WRITE)
** Last Mounted on /shogidb3
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=37 (1545472 should be 1447168)
CORRECT? no

INCORRECT BLOCK COUNT I=47 (1701248 should be 1586560)
CORRECT? no

...

** Phase 2 - Check Pathnames
UNALLOCATED  I=213  OWNER=root MODE=100644
SIZE=614897920 MTIME=Apr 24 03:52 2004
FILE=/pb1b2CDB5x6:MTA:P2:MV1024:LOC33.cdb2

UNEXPECTED SOFT UPDATE INCONSISTENCY

REMOVE? no

UNALLOCATED  I=212  OWNER=root MODE=100644
SIZE=508980463 MTIME=Apr 24 03:49 2004
FILE=/pCDB5x6:MTA:P2:MV1024:LOC33.cdb2

UNEXPECTED SOFT UPDATE INCONSISTENCY

REMOVE? no

...

** Phase 3 - Check Connectivity
** 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 FILE 51 MARKED FREE
ALLOCATED FILE 54 MARKED FREE
ALLOCATED FILE 59 MARKED FREE
BLK(S) MISSING IN BIT MAPS
SALVAGE? no

######################
# fsck -F -y /shogidb3 
###################### 

** /dev/ad0s4e (NO WRITE)
** Last Mounted on /shogidb3
** 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

SUMMARY INFORMATION BAD
SALVAGE? no

ALLOCATED FILE 51 MARKED FREE
ALLOCATED FILE 54 MARKED FREE
ALLOCATED FILE 59 MARKED FREE
BLK(S) MISSING IN BIT MAPS
SALVAGE? no

58 files, 8715685 used, 9833760 free (40 frags, 1229215 blocks, 0.0% fragmentation)