Re: Linux kernel - Libata bad block error handling to user mode program
From: Greg Freemyer
Date: Fri Mar 05 2010 - 01:01:26 EST
> Please let me know if you can prove data corruption. I'm writing a
> sophisticated storage app and would like to know if kernel has such a
> defect. My bet is it's just a drive that is slowly remapping.
> - Mike
For clarity, most ATA class disk drives are spec'ed to have one
non-recoverable error per 150TB or so of writes. Disk drives do blind
writes. (ie. They are not verified). So we should all expect to have
the occasional silent data corruption on write. The problem is
compounded with bad cables, controllers, RAM, etc.
The only way for the linux kernel even attempt to fix that is for it
to do a read verify on everything it writes. For the vast majority of
uses that is just not acceptable for performance reasons.
OTOH, if data integrity is of the utmost for you, then you should
maintain a md5hash or similar for your critical files and verify them
any time you make a copy. btrfs may offer a auto read-verify. I
don't know much about btrfs.
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
Preservation and Forensic processing of Exchange Repositories White Paper -
The Norcross Group
The Intersection of Evidence & Technology
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/