e2fsck compatibility problem with 2.4.17?

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* e2fsck compatibility problem with 2.4.17?
@ 2002-02-19 14:11 Joao Guimaraes da Costa
  2002-02-19 21:11 ` Mohammad A. Haque
  2002-02-19 21:15 ` Andreas Dilger
  0 siblings, 2 replies; 5+ messages in thread
From: Joao Guimaraes da Costa @ 2002-02-19 14:11 UTC (permalink / raw)
  To: linux-kernel

Hi,

I am having a problem that might be due to an incompatibility between
e2fsck and kernel 2.4.17.

My machine has a redhat kernel 2.4.3-12 and a kernel 2.4.17 I have 
recently built from source.

While doing a routine filesystem check at boot time (running kernel 
2.4.17), e2fsck found a problem with one of the partitions (I am using 
e2fsck 1.25 from the redhat rawhide rpm  e2fsprogs-1.25-2.i386.rpm).

I decided not to fix the problem and checked it with a different kernel
and version 1.19 of e2fsck. In both cases, the partition was clean.

So, I get:

kernel     e2fsck    result
2.4.17      1.25     problem
2.4.3-12    1.25      OK
2.4.3-12    1.19      OK

Are there any know incompatibilities between kernel 2.4.17 and e2fsck
1.25? Right now, I am not sure if the filesystem is damaged or not!

The error I get is the following:
1) e2fsck gets stuck after only checking 2.5% of the partition. It stays
   there for about 5 minutes doing clik-clak noises until starting giving
errors
2) First error is:
Block 32783 - 32791 (attempt to read block from filesystem resulted in
short read) while doing inode scan.
3) Then in Pass 2:
resources in /src/linux-2.4.3/drivers/acpi (1894) has deleted/unused
inode 16435.
And it keeps giving many similar messages....

If it is useful I can try to get the full output. This has been 100% 
reproducible in my system.

Thank you,
	-Joao
.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: e2fsck compatibility problem with 2.4.17?
  2002-02-19 14:11 e2fsck compatibility problem with 2.4.17? Joao Guimaraes da Costa
@ 2002-02-19 21:11 ` Mohammad A. Haque
  2002-02-19 21:15 ` Andreas Dilger
  1 sibling, 0 replies; 5+ messages in thread
From: Mohammad A. Haque @ 2002-02-19 21:11 UTC (permalink / raw)
  To: Joao Guimaraes da Costa; +Cc: linux-kernel


On Tuesday, February 19, 2002, at 09:11 , Joao Guimaraes da Costa wrote:

>
> Hi,
>
> I am having a problem that might be due to an incompatibility between
> e2fsck and kernel 2.4.17.
>
> My machine has a redhat kernel 2.4.3-12 and a kernel 2.4.17 I have 
> recently built from source.
>
> While doing a routine filesystem check at boot time (running kernel 
> 2.4.17), e2fsck found a problem with one of the partitions (I am using 
> e2fsck 1.25 from the redhat rawhide rpm  e2fsprogs-1.25-2.i386.rpm).
>
> I decided not to fix the problem and checked it with a different kernel
> and version 1.19 of e2fsck. In both cases, the partition was clean.
>
> So, I get:
>
> kernel     e2fsck    result
> 2.4.17      1.25     problem
> 2.4.3-12    1.25      OK
> 2.4.3-12    1.19      OK
>
> Are there any know incompatibilities between kernel 2.4.17 and e2fsck
> 1.25? Right now, I am not sure if the filesystem is damaged or not!
>
> The error I get is the following:
> 1) e2fsck gets stuck after only checking 2.5% of the partition. It stays
>   there for about 5 minutes doing clik-clak noises until starting giving
> errors
> 2) First error is:
> Block 32783 - 32791 (attempt to read block from filesystem resulted in
> short read) while doing inode scan.
> 3) Then in Pass 2:
> resources in /src/linux-2.4.3/drivers/acpi (1894) has deleted/unused
> inode 16435.
> And it keeps giving many similar messages....
>
> If it is useful I can try to get the full output. This has been 100% 
> reproducible in my system.

I just lost my system running 2.4.17/ext3 w/ e2fsprogs 1.25 last week 
with similar reports from e2fsck. Though I attributed my problem to my 
hard drive trying to tell me it was about to die because I got the same 
errors when booted into rescue mode from a RH 7.2 CD.

--

=====================================================================
Mohammad A. Haque                              http://www.haque.net/
                                                mhaque@haque.net

   "Alcohol and calculus don't mix.             Developer/Project Lead
    Don't drink and derive." --Unknown          http://www.themes.org/
                                                batmanppc@themes.org
=====================================================================


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: e2fsck compatibility problem with 2.4.17?
  2002-02-19 14:11 e2fsck compatibility problem with 2.4.17? Joao Guimaraes da Costa
  2002-02-19 21:11 ` Mohammad A. Haque
@ 2002-02-19 21:15 ` Andreas Dilger
  2002-02-20  3:13   ` Joao Guimaraes da Costa
  1 sibling, 1 reply; 5+ messages in thread
From: Andreas Dilger @ 2002-02-19 21:15 UTC (permalink / raw)
  To: Joao Guimaraes da Costa; +Cc: linux-kernel

On Feb 19, 2002  08:11 -0600, Joao Guimaraes da Costa wrote:
> I am having a problem that might be due to an incompatibility between
> e2fsck and kernel 2.4.17.
> 
> My machine has a redhat kernel 2.4.3-12 and a kernel 2.4.17 I have 
> recently built from source.
> 
> While doing a routine filesystem check at boot time (running kernel 
> 2.4.17), e2fsck found a problem with one of the partitions (I am using 
> e2fsck 1.25 from the redhat rawhide rpm  e2fsprogs-1.25-2.i386.rpm).
> 
> I decided not to fix the problem and checked it with a different kernel
> and version 1.19 of e2fsck. In both cases, the partition was clean.
> 
> So, I get:
> 
> kernel     e2fsck    result
> 2.4.17      1.25     problem
> 2.4.3-12    1.25      OK
> 2.4.3-12    1.19      OK
> 
> Are there any know incompatibilities between kernel 2.4.17 and e2fsck
> 1.25? Right now, I am not sure if the filesystem is damaged or not!
> 
> The error I get is the following:
> 1) e2fsck gets stuck after only checking 2.5% of the partition. It stays
>    there for about 5 minutes doing clik-clak noises until starting giving
> errors
> 2) First error is:
> Block 32783 - 32791 (attempt to read block from filesystem resulted in
> short read) while doing inode scan.
> 3) Then in Pass 2:
> resources in /src/linux-2.4.3/drivers/acpi (1894) has deleted/unused
> inode 16435.

Well, this clik-clak noise sounds like a hardware problem.  I don't know
why it would only show up under 2.4.17 and not 2.4.3.

Can you try "dd if=/dev/hdX of=/dev/null bs=4k" to see if this completes
under both kernels?  Any messages in 'dmesg' that look like IDE errors?

The one thing I also thought of was that kernels 2.4.10+ have the block
devices in page cache, and some people have problems with ulimits when
reading >2GB from the device, but that wouldn't affect block 32783...

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: e2fsck compatibility problem with 2.4.17?
  2002-02-19 21:15 ` Andreas Dilger
@ 2002-02-20  3:13   ` Joao Guimaraes da Costa
  2002-02-20 11:31     ` Jan Niehusmann
  0 siblings, 1 reply; 5+ messages in thread
From: Joao Guimaraes da Costa @ 2002-02-20  3:13 UTC (permalink / raw)
  To: Andreas Dilger; +Cc: linux-kernel

Hi,

I have tried what you suggested.

I tried "dd if=/dev/hdX of=/dev/null bs=4k" under kernel 2.4.3 and got:
dd: reading `/dev/hda7': Input/output error
32792+0 records in
32792+0 records out

After doing this I got the following error with dmesg:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262336end_request: I/O error, dev 03:07 (hda), sector 262336

This was the only disk error and it was there only after the "dd" command.

---
The same "dd" command under kernel 2.4.17 gives a similar error message 
although with a different record number.

dd: reading `/dev/hda7': Input/output error
32772+0 records in
32772+0 records out

The errors from dmesg are below. The "VFS: Disk change detected on 
device ide1(22,0)" error was there before the "dd" command, and it shows 
continuosly:


VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262176end_request: I/O error, dev 03:07 (hda), sector 262176
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262184end_request: I/O error, dev 03:07 (hda), sector 262184
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262192end_request: I/O error, dev 03:07 (hda), sector 262192
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262200end_request: I/O error, dev 03:07 (hda), sector 262200
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262208end_request: I/O error, dev 03:07 (hda), sector 262208
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262216end_request: I/O error, dev 03:07 (hda), sector 262216
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262224end_request: I/O error, dev 03:07 (hda), sector 262224
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262232end_request: I/O error, dev 03:07 (hda), sector 262232
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262240end_request: I/O error, dev 03:07 (hda), sector 262240
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262248end_request: I/O error, dev 03:07 (hda), sector 262248
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262256end_request: I/O error, dev 03:07 (hda), sector 262256
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262264end_request: I/O error, dev 03:07 (hda), sector 262264
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262272end_request: I/O error, dev 03:07 (hda), sector 262272
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262280end_request: I/O error, dev 03:07 (hda), sector 262280
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262288end_request: I/O error, dev 03:07 (hda), sector 262288
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262296end_request: I/O error, dev 03:07 (hda), sector 262296
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262304end_request: I/O error, dev 03:07 (hda), sector 262304
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262312end_request: I/O error, dev 03:07 (hda), sector 262312
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262320end_request: I/O error, dev 03:07 (hda), sector 262320
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262328end_request: I/O error, dev 03:07 (hda), sector 262328
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, CHS=10793/1/175, 
sector=262336end_request: I/O error, dev 03:07 (hda), sector 262336
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)


It is also interesting that with kernel 2.4.3, I only get one error from 
using the "dd" command. The drive makes some noise and then it stops 
with the error above.
Under 2.4.17, it seems that it tries harder and I get more errors. The 
drive stays there making noise. (BTW, the noise is a set of 4 x runck 
plus 4 x ham! It seems each set corresponds to an error on dmesg.)

Also, I do not really understand what the error "VFS: Disk change 
detected on device ide1(22,0)" means.

The results point to a damaged disk, however, it is still interesting 
that this is not detected by e2fsck under the 2.4.3 kernel.
After doing the "dd" command and getting all this errors, I have checked 
the filesystem again with similar results. It is "clean" if running 
kernel 2.4.3!

Thanks,
	-Joao

Andreas Dilger wrote:
> On Feb 19, 2002  08:11 -0600, Joao Guimaraes da Costa wrote:
> 
>>I am having a problem that might be due to an incompatibility between
>>e2fsck and kernel 2.4.17.
>>
>>My machine has a redhat kernel 2.4.3-12 and a kernel 2.4.17 I have 
>>recently built from source.
>>
>>While doing a routine filesystem check at boot time (running kernel 
>>2.4.17), e2fsck found a problem with one of the partitions (I am using 
>>e2fsck 1.25 from the redhat rawhide rpm  e2fsprogs-1.25-2.i386.rpm).
>>
>>I decided not to fix the problem and checked it with a different kernel
>>and version 1.19 of e2fsck. In both cases, the partition was clean.
>>
>>So, I get:
>>
>>kernel     e2fsck    result
>>2.4.17      1.25     problem
>>2.4.3-12    1.25      OK
>>2.4.3-12    1.19      OK
>>
>>Are there any know incompatibilities between kernel 2.4.17 and e2fsck
>>1.25? Right now, I am not sure if the filesystem is damaged or not!
>>
>>The error I get is the following:
>>1) e2fsck gets stuck after only checking 2.5% of the partition. It stays
>>   there for about 5 minutes doing clik-clak noises until starting giving
>>errors
>>2) First error is:
>>Block 32783 - 32791 (attempt to read block from filesystem resulted in
>>short read) while doing inode scan.
>>3) Then in Pass 2:
>>resources in /src/linux-2.4.3/drivers/acpi (1894) has deleted/unused
>>inode 16435.
>>
> 
> Well, this clik-clak noise sounds like a hardware problem.  I don't know
> why it would only show up under 2.4.17 and not 2.4.3.
> 
> Can you try "dd if=/dev/hdX of=/dev/null bs=4k" to see if this completes
> under both kernels?  Any messages in 'dmesg' that look like IDE errors?
> 
> The one thing I also thought of was that kernels 2.4.10+ have the block
> devices in page cache, and some people have problems with ulimits when
> reading >2GB from the device, but that wouldn't affect block 32783...
> 
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
> 
> .
> 
> 




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: e2fsck compatibility problem with 2.4.17?
  2002-02-20  3:13   ` Joao Guimaraes da Costa
@ 2002-02-20 11:31     ` Jan Niehusmann
  0 siblings, 0 replies; 5+ messages in thread
From: Jan Niehusmann @ 2002-02-20 11:31 UTC (permalink / raw)
  To: Joao Guimaraes da Costa; +Cc: Andreas Dilger, linux-kernel

On Tue, Feb 19, 2002 at 09:13:37PM -0600, Joao Guimaraes da Costa wrote:
> It is also interesting that with kernel 2.4.3, I only get one error from 
> using the "dd" command. The drive makes some noise and then it stops 
> with the error above.
> Under 2.4.17, it seems that it tries harder and I get more errors. The 
> drive stays there making noise. (BTW, the noise is a set of 4 x runck 
> plus 4 x ham! It seems each set corresponds to an error on dmesg.)

Just a guess: 2.4.17 may use a different read-ahead algorithmn than
2.4.3, so while dd is reading only one block (and stops if there is a
failure), 2.4.17 tries to read several blocks at once and writes more
than one error message to the log file.

Note that e2fsck reports an error in the range 32783 - 32791, while dd
on 2.4.3 has problems with 32792. So the (first) bad block may be 32792,
but e2fsck gets an error for a block <=32791.

Question is, why does e2fsck get an error from the kernel when it tries
to read (for example) 32791, the kernel can read 32791 without problems,
but gets a hard drive error for 32792? 

Note that this may be all wrong, I currently do not have the time to
read the kernel source and try to verify it.

Jan

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-02-20 11:31 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-19 14:11 e2fsck compatibility problem with 2.4.17? Joao Guimaraes da Costa
2002-02-19 21:11 ` Mohammad A. Haque
2002-02-19 21:15 ` Andreas Dilger
2002-02-20  3:13   ` Joao Guimaraes da Costa
2002-02-20 11:31     ` Jan Niehusmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox