Messages in this thread | | | Date | Tue, 3 Nov 1998 16:00:03 GMT | From | "Stephen C. Tweedie" <> | Subject | Re: 2.1.126: Possible bug in fschk/corrupted inode handling |
| |
Hi,
On Mon, 02 Nov 1998 15:38:06 GMT, Meino Christian Cramer <root@solfire.ludwigsburg.netsurf.de> said:
> Hi ! > The following happens: > Writing to one of the log files in /var/adm/. produces > a "hardware error: MEDIUM ERROR -- cannot write to block XYZ"
> e2fsck -c /dev/<sda2>
> to check everything for not useable blocks. This SHOULD also include > defect blocks into the badblock inode.
> Again the sound nasty soudn a the same block was reported being defect.
I have come across disks before which work just perfectly if you read them using a linear read, but on which bad sectors are found repeatably if you perform random access reads. Badblocks is a sequential scan, and in cases where the disk alignment is off, it's quite possible that media errors will be missed by it but hit by a random access later on.
--Stephen
- 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/
| |