public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Tejun Heo <htejun@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, 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 10:44:11 +0300	[thread overview]
Message-ID: <200707131044.20466.caglar@pardus.org.tr> (raw)
In-Reply-To: <4696EDAB.10404@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

13 Tem 2007 Cum tarihinde, Tejun Heo şunları yazmıştı: 
> >> 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.

It seems reboot/shutdown has no effect on reallocated sectors. After 5 rebot/5 
shutdown it didn't change at all.

zangetsu ~ # smartctl -a /dev/sda | grep Reall
  5 Reallocated_Sector_Ct   0x0033   067   067   010    Pre-fail  
Always       -       314
196 Reallocated_Event_Count 0x0032   067   067   000    Old_age   
Always       -       314

Cheers
-- 
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-13  7:44 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
2007-07-13  7:44               ` S.Çağlar Onur [this message]
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=200707131044.20466.caglar@pardus.org.tr \
    --to=caglar@pardus.org.tr \
    --cc=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox