All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
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: Fri, 13 Jul 2007 12:12:43 +0900	[thread overview]
Message-ID: <4696EDAB.10404@gmail.com> (raw)
In-Reply-To: <20070712195255.GA6015@ucw.cz>

Pavel Machek wrote:
>>>> 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.
> 
> Hmm... cut the power while writing is doable from OS and might force
> reallocations?

Hmmm... We don't have any pending write when power goes out and I don't
emergency unload can directly increase reallocation count.  It can
shorten lifespan of the head tho.

> You might want to check if number of reallocated sectors increases
> with shutdowns/reboots.

I'm curious too.

-- 
tejun

  reply	other threads:[~2007-07-13  3:12 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
2007-07-12 19:52           ` Pavel Machek
2007-07-13  3:12             ` Tejun Heo [this message]
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=4696EDAB.10404@gmail.com \
    --to=htejun@gmail.com \
    --cc=caglar@pardus.org.tr \
    --cc=hancockr@shaw.ca \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.