Re: "Forever" fsck?

On Sun, 27 Aug 2006 12:50:54 -0500, Dances With Crows wrote:

If you're sure that there's no
hardware problem, the quickest/easiest way to get back to normal is
probably to mke2fs -j the partition.

I am *not* sure that there's no hardware problem. I did find on the
console messages like:

SCSI error : <3 0 0 0> return code = 0x10070000
end_request: I/O error, dev sdd, sector 976794177
SCSI error : <3 0 0 0> return code = 0x10070000
end_request: I/O error, dev sdd, sector 976794185
SCSI error : <3 0 0 0> return code = 0x10070000
end_request: I/O error, dev sdd, sector 976794193
SCSI error : <3 0 0 0> return code = 0x10070000
end_request: I/O error, dev sdd, sector 976794201
SCSI error : <3 0 0 0> return code = 0x10070000
end_request: I/O error, dev sdd, sector 976794209
...

but these only occurred very early in the process. Since the first few
runs of fsck, these have ceased. In fact, I think that this was from when
I ran fsck with the badblocks option, come to think of it.

One more piece of information: the fsck is now (yes, I left it running for
a couple of days!) in an infinite loop. It repeats:

Restarting e2fsck from the beginning...
Pass 1: Checking inodes, blocks, and sizes
Inode 7 has illegal block(s). Clear? yes

Illegal block #20494 (1156635280) in inode 7. CLEARED.
Illegal block #20495 (1137955446) in inode 7. CLEARED.
Illegal block #20496 (1156635280) in inode 7. CLEARED.
Illegal block #20526 (1156616080) in inode 7. CLEARED.
Illegal block #20527 (1156616064) in inode 7. CLEARED.
Illegal block #20528 (1156616064) in inode 7. CLEARED.
Illegal block #20686 (1137955446) in inode 7. CLEARED.
Illegal block #20687 (1137955446) in inode 7. CLEARED.
Illegal block #20688 (1137955446) in inode 7. CLEARED.
Illegal block #20689 (1156857862) in inode 7. CLEARED.
Illegal block #20719 (1137955448) in inode 7. CLEARED.
Too many illegal blocks in inode 7.
Clear inode? yes

Restarting e2fsck from the beginning...
Pass 1: Checking inodes, blocks, and sizes
Inode 7 has illegal block(s). Clear? yes

...

with the same block numbers now.

I didn't use the -k option when I last ran fsck with the badblocks option.
I've just started that now. I'm curious if it'll help (if the problem
blocks will be marked bad and subsequently ignored).

- Andrew


.

Relevant Pages

  • Re: Data corruption on IDE disk via USB.
    ... >> I have an external hard drive with an IDE interface. ... >> when copying big files to the drive, ... Inode 8 has illegal block. ... Illegal block #4255 in inode 8. ...
    (Linux-Kernel)
  • Re: Xconfig
    ... paravirtualized 32-bit on 64-bit host? ... I thought ur facing issues with your root file system. ... Resize inode not valid. ... Illegal block #-1 in inode 54473213. ...
    (RedHat)
  • Really scary problem
    ... The server volume is a 6 disk SATA RAID array hosted by a Highpoint ... Feb 26 03:25:15 localhost kernel: attempt to access beyond end of device ... with inode 8, says there are too many illegal blocks in the inode, clears ... Illegal block #5399 in inode 8. ...
    (alt.os.linux)
  • "Forever" fsck?
    ... Restarting e2fsck from the beginning... ... Inode 7 has illegal block. ... Illegal block #20494 in inode 7. ... problem leaving the fsck running (though I am worried that the process ...
    (comp.os.linux.hardware)
  • Re: Can I create a link to an inode?
    ... The file doesn't occupy the entire last sector in most filesystems. ... Maybe that's what was meant originally as garbage bytes - the whole file ... inode. ...
    (Fedora)