From: Jonathan Briggs <jbriggs@esoft.com>
To: Clay Barnes <clay.barnes@gmail.com>
Cc: Hans Reiser <reiser@namesys.com>,
rudekjan@freenet.de, reiserfs-list@namesys.com
Subject: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
Date: Mon, 30 Jan 2006 23:37:15 -0700 [thread overview]
Message-ID: <43DF059B.5030502@esoft.com> (raw)
In-Reply-To: <43DED6E1.3060509@gmail.com>
Clay Barnes wrote:
> To amplify what Hans (accurately) wrote, once you see bad sectors,
> that means that you already have many more than you see, and that your
> hard drive is all out of spare sectors to silently swap out for when
> it finds one.
>
> Basically, there's so much wrong with the surface that your hard drive
> can't hide any more flaws, and has given up trying.
>
> Hans is right: If you see a single bad sector, the drive is
> considered unsafe and trash for even the tightest owner.
I don't believe that's quite true. It's my understanding that a drive
may have a correctable read error. The data may be too damaged to read
from that sector, but rewriting the sector can repair it or remap it to
a new undamaged area. The drive cannot make up the lost data though, so
it must report the error.
The damage can come from a partial write during power down or from data
that was marginal to start with and hadn't been read in a long time
(Drives will remap sectors even on successful reads, when they have to
use too much error correction to get the data, but don't generally do
full surface sweeps to check. SMART can be told to do full surface
checks, however.)
Don't take the existence of a single bad sector as proof that the drive
is trash. Instead, check the SMART status and look at the remap rates
and error rates. SMART should have a nice summary for you too, either
OK, FAILING or FAILED (or similar phrases).
next prev parent reply other threads:[~2006-01-31 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 1:15 Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic rudekjan
2006-01-31 1:47 ` Hans Reiser
2006-01-31 3:17 ` Clay Barnes
2006-01-31 6:37 ` Jonathan Briggs [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-31 13:52 abc1237
2006-01-31 14:39 ` Chet Hosey
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=43DF059B.5030502@esoft.com \
--to=jbriggs@esoft.com \
--cc=clay.barnes@gmail.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rudekjan@freenet.de \
/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.