[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: EXT3-fs error



Hi,

On Sun, Jan 20, 2002 at 05:56:48PM -0800, Louis Hopcraft wrote:
 
> I'm using RedHat 7.2 now and haven't have any problems until today.  I
> can still boot into the system at this time, but cannot load X at all. 
> I'm getting the following error message when I try to run fsck.
> 
> /contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks and sizes
> Error reading block 1277964 (Attempt to read block from filesystem
> resulted in a short read) while doing inode scan.  Ignore error<y>?

So fsck tried to read part of the filesystem and got an IO failure.

> below is some output from dmesg:
> 
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=81423,
> sector=81360

Messages coming back from the IDE driver indicating fatal media
errors: you've got bad sectors on the disk.

> end_request: I/O error, dev 03:41 (hdb), sector 10223712

IDE passes the error back up to the filesystem...

> EXT3-fs error (device ide0(3,65)): ext3_get_inode_loc: unable to read
> inode block - inode=636706, block=1277964
> EXT3-fs error (device ide0(3,65)) in ext3_reserve_inode_write: IO
> failure
> EXT3-fs error (device ide0(3,65)) in ext3_new_inode: IO failure

... and the filesystem logs the failure and passes EIO back up to the
calling application.

The kernel is working exactly as expected in the presence of
unrecoverable disk failure.

Cheers,
 Stephen





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]