large file problem in rh7.1

[ken at kg293.net (Ken Gosier)]

On Wed, 27 Feb 2002, Greg Galperin wrote:

> If that doesn't work it could even be some problems with those blocks
> on disk.  After trying the usual fsck, you can run 'e2fsck -c' to
> detect and mark off bad blocks.


OK, so just to follow up 1 more time: I had posted a couple weeks ago
about a 80 MB file I had trouble with. It wouldn't cp, wc, or anything,
it always had an I/O error or a hang at around 50 MB.

So I used

dd bs=100k < /dev/hda5 > /dev/null

as suggested in 1 of the replies, as a way of checking how many blocks got
copied. (I may be using wrong terminology there. :-) This also had an I/O
error in the same file.

The solution came by using e2fsck -c, as suggested by Greg Galperin above.
(Thanks! :) I'm now able to cp, gzip, do whatever to the file. I'm
including the output below. (The misbehaving file is /home/ken/ali.mp3.)

Many thanks again for all the replies/help--

-- 
Ken Gosier
ken at kg293.net



[root at kg293 /sbin]# ./e2fsck -c /dev/hda5
e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
Checking for bad blocks (read-only test): done
Pass 1: Checking inodes, blocks, and sizes
Duplicate blocks found... invoking duplicate block passes.
Pass 1B: Rescan for duplicate/bad blocks
Duplicate/bad block(s) in inode 177371: 449281
Pass 1C: Scan directories for inodes with dup blocks.
Pass 1D: Reconciling duplicate blocks
(There are 1 inodes containing duplicate/bad blocks.)

File /home/ken/ali.mp3 (inode #177371, mod time Mon Feb 18 22:07:51 2002)
  has 1 duplicate block(s), shared with 1 file(s):
        <The bad blocks inode> (inode #1, mod time Sat Mar 16 17:39:09 2002)
Clone duplicate/bad blocks<y>? yes

Error reading block 449281 (Attempt to read block from filesystem resulted in short read).  Ignore error<y>? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (162, counted=161).
Fix<y>? yes

Free blocks count wrong for group #13 (162, counted=163).
Fix<y>? yes


/: ***** FILE SYSTEM WAS MODIFIED *****
/: 107155/320640 files (1.6% non-contiguous), 487433/640584 blocks