a subtle bug of ext2 or e2fsck ? (fwd)
Dave Meyer (dmeyer@virtc.com)
Sun, 19 Sep 1999 13:18:56 -0400
In article <Pine.SOL.3.96.990918171311.4405C-100000@suphys.physics.usyd.edu.au> you write:
> 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.
>
> Do you have any idea what is happening here? Is there any tool that I
> still can recover my data on /dev/hda3? Debugfs and dumpe2fs all failed
> to open the file system on /dev/hda3. I was too stupid to backup my files.
We had a similar problem when our NFS server crashed hard - one of the
partitions reported this same error, and also something about "Are you
sure this isn't a zero-length partition?". What worked for us was to
use the `-b' option to e2fsck, which forced e2fsck to look at a
different superblock.
> Your help is greatly appreciated.
I hope my help is greatly useful.
Dave
--
David M. Meyer
meyer@virtc.com
-
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/