From: Tejun Heo <htejun@gmail.com>
To: Tomas Lund <tlund@nxs.se>
Cc: Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: Need help understanding SATA error message.
Date: Mon, 31 Mar 2008 09:59:27 +0900 [thread overview]
Message-ID: <47F0376F.2090000@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0803301659300.5510@envy.nxs.se>
Tomas Lund wrote:
> On Fri, 28 Mar 2008, Mark Lord wrote:
>
>> One thing to try, if you have 12000 seconds to spare, :) is to simply
>> try this:
>>
>> cat /dev/zero > /dev/sdX
>> sync
>> hdparm -F /dev/sdX
>>
>> And see if that completes without error. If it does, then the drive
>> may be fine.
>>
>> Software bugs are always possible, but do seem unlikely in this case.
>> But then, so does a hardware failure seem unlikely on a new drive.
>
> completed without errors, no sectors reallocated...
Can you put the driver under IO load test involving lots of writes and
flushes (mounting as ext3 w/ barrier=1 and doing lots of copying should
achieve it) and see whether the error is still reproducible?
--
tejun
next prev parent reply other threads:[~2008-03-31 0:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 7:04 Need help understanding SATA error message Tomas Lund
2008-03-28 13:40 ` Jeff Garzik
2008-03-28 14:28 ` Tomas Lund
2008-03-28 15:49 ` Mark Lord
2008-03-28 15:59 ` Mark Lord
2008-03-28 22:21 ` Tomas Lund
2008-03-29 3:50 ` Mark Lord
2008-03-30 15:01 ` Tomas Lund
2008-03-31 0:59 ` Tejun Heo [this message]
2008-03-31 14:53 ` Mark Lord
2008-04-01 0:26 ` Tejun Heo
2008-04-01 2:01 ` Mark Lord
2008-04-01 7:11 ` Tomas Lund
2008-04-01 12:05 ` Mark Lord
2008-04-01 16:15 ` Tejun Heo
2008-04-02 5:17 ` Tomas Lund
2008-04-03 10:39 ` Tomas Lund
2008-04-11 6:16 ` Tejun Heo
2008-03-29 3:54 ` Mark Lord
2008-03-29 10:39 ` Tomas Lund
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=47F0376F.2090000@gmail.com \
--to=htejun@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=tlund@nxs.se \
/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.