From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: caglar@pardus.org.tr, Robert Hancock <hancockr@shaw.ca>,
LKML <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: SATA exceptions
Date: Wed, 11 Jul 2007 13:20:15 -0400 [thread overview]
Message-ID: <4695114F.1010206@tmr.com> (raw)
In-Reply-To: <46928066.7000705@gmail.com>
Tejun Heo wrote:
> Hello,
>
> S.Çağlar Onur wrote:
>> 07 Tem 2007 Cts tarihinde, Robert Hancock şunları yazmıştı:
>>> It's not the free space on the drive that matters, it's the number of
>>> free sectors in the spare sector pool on the drive, which is invisible
>>> to software.
>>>
>>> Your SMART log shows 309 reallocated sectors. That seems somewhat high..
>> Ah sorry to misinterpret the content:), its a quiet new piece of hardware (at
>> most ~1.5 month old) and "Reallocated_Event_Count" constantly increases
>> (currently its increased to 313) and although i'm not 100 percent sure these
>> errors only occured with kernels > 2.6.18 (or 2.6.18 didn't report these
>> cause according to kern.log these only visible with 2.6.22+)
>
> OS and driver can't really do much about the reallocation event. Some
> number of reallocations is okay but if you it going up constantly, you
> probably have a dying disk.
>
Or, as I learned the hard way, if you have the problem on all drives
sharing a power supply, a power issue.
>> We bought 3 HP Pavillon dv2385ea and one of them only runs with 2.6.18 and its
>> smartctl output follows as a reference;
>>
>> 5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail
>> 196 Reallocated_Event_Count 0x0032 253 253 000 Old_age
>
> Hmm... This is pretty high too. Do the counts increase on this machine too?
>
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-07-11 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.hBFih6KVHDFsBf6Qfg6XispiIuY@ifi.uio.no>
[not found] ` <fa.50UJZSgW/ChUl7O1Zks6ydq/1js@ifi.uio.no>
[not found] ` <fa.NhBdOmH9+RkW+QO72+TjPRwEKj0@ifi.uio.no>
2007-07-07 18:05 ` SATA exceptions Robert Hancock
2007-07-07 21:35 ` S.Çağlar Onur
2007-07-09 18:37 ` Tejun Heo
2007-07-09 19:06 ` S.Çağlar Onur
2007-07-11 17:20 ` Bill Davidsen [this message]
2007-07-12 19:52 ` Pavel Machek
2007-07-13 3:12 ` Tejun Heo
2007-07-13 7:44 ` S.Çağlar Onur
2007-07-11 20:31 ` Mark Lord
2007-07-12 3:13 ` Tejun Heo
2007-07-05 21:46 S.Çağlar Onur
2007-07-06 1:52 ` Tejun Heo
2007-07-06 11:43 ` S.Çağlar Onur
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=4695114F.1010206@tmr.com \
--to=davidsen@tmr.com \
--cc=caglar@pardus.org.tr \
--cc=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox