> hi, there,
>
> I recently have had some troubles with my file systems. e2fsck (1.14 )
> reports ``Error reading block #### (Attempt to read block from filesystem
> resulted in short read) while doing inode scan. Ignore error<y>". I
> answered 'y'. However, I got more and more such errors. Eventually, I got
> ''Attempt to read black from filesystem resulted in short read while
> trying to open /dev/hda3''.
>
> I have three partitions from dev/hda1 to /dev/hda3 and I have the same
> problems with all three partitions. I reformatted dev/hda1 and it seems
> fine. So this is not a hardware problem.
The same error occured to me when I recompiled the e2fsprogs-1.10, from
RedHat 5.1 CD#2. when I tried to e2fsck partitions bigger than 2GB, it
gave me the above response. I tracked it down to the llseek function call
which tries to read the inode table after the 2GB barrier.
In general, what shall one do if he/she wants to recompile e2fsprogs
tarball?
I use RedHat5.1 (everything as installed by RedHat:kernel 2.0.34,
glibc-2, etc.)
Hardware: a Pentium 200MHz,
Asus-SP97V motherboard,
64MB of RAM,
2MB dedicated to onboard VGA controller.
10G,12G Quantum IDE disks.
all of hardware components work correctly ( and e2fsck, as I run it from
default location which is compiled in RedHat, but home-compiled e2fsck
fails).
Any ideas?
--masu
-
This message is Ozone-Friendly.
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/