0 bad blocks ???

Project:Linux software
Component:Documentation
Category:support request
Priority:normal
Assigned:Unassigned
Status:active
Related pages:#94: e2fsck: file system check
Description

While running e2fsck, I got 31 errors like this:

Error reading block 34308211 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan.  Ignore error? yes

Force rewrite? yes

However, the summary at the end says:

Error reading block 44400837 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error? yes

Force rewrite? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(37312406--37313430)
Fix? yes

Free blocks count wrong for group #1138 (31485, counted=32510).
Fix? yes

Free blocks count wrong (175514766, counted=175515791).
Fix? yes

***** FILE SYSTEM WAS MODIFIED *****

73 inodes used (0.00%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 58/58/40
68674209 blocks used (28.12%)
0 bad blocks
50 large files

58 regular files
6 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
64 files

0 bad blocks ???
What does this summary mean?