From: Mark Lord <kernel@teksavvy.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Mark Lord <liml@rtr.ca>
Subject: Re: If I have a single bad sector, how many failed reads should simple dd report?
Date: Fri, 09 Jul 2010 21:19:21 -0400 [thread overview]
Message-ID: <4C37CA99.1040104@teksavvy.com> (raw)
In-Reply-To: <AANLkTimWfp4mLF9DCpxtnnUQsYQ08gXmh491EfhARe1x@mail.gmail.com>
On 09/07/10 03:04 PM, Greg Freemyer wrote:
..
>> When I re-ran it, /var/log/messages reported 10 bad logical blocks.
>> And even worse, dd reported 20 bad blocks. I examined the data dd
>> read and it had 80KB of zero'ed out data. So that's 160 sectors worth
>> of data lost because of a single bad sector. At most I was expecting
>> 4KB of zero'ed out data.
..
That's just the standard, undesirable result of the current SCSI EH
when used with libata for (mainly) desktop computers.
I have patches (against older kernels) to fix it, but have yet to
get both myself and James B. interested enough simultaneously to
actually get the kernel fixed. :)
..
> cmp -bl clean.dd corrupt.dd> delta.log
>
> Looking at delta.log, the bytes start disagreeing 4 bytes prior to the
> sector boundary. How can that be?
..
Dunno. That could be a different problem.
I've seen the odd scattered report of data corruption on ext3/ext4
with large data sets, but don't know what the root causes were.
Cheers
next prev parent reply other threads:[~2010-07-10 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 17:14 If I have a single bad sector, how many failed reads should simple dd report? Greg Freemyer
2010-07-09 19:04 ` Greg Freemyer
2010-07-10 1:19 ` Mark Lord [this message]
2010-07-10 1:24 ` Mark Lord
2010-07-10 14:14 ` James Bottomley
2010-07-11 12:58 ` Greg Freemyer
2010-07-13 19:07 ` Mark Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C37CA99.1040104@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=greg.freemyer@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.