From: Zan Lynx <zlynx@acm.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: ric@emc.com, Christian Kujau <lists@nerdbynature.de>,
kgp <jyotiv@tataelxsi.co.in>,
reiserfs-devel@vger.kernel.org
Subject: Re: bad block management
Date: Thu, 03 Apr 2008 18:14:32 -0600 [thread overview]
Message-ID: <1207268072.379391.7.camel@localhost> (raw)
In-Reply-To: <47F29257.3000502@suse.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Tue, 2008-04-01 at 15:51 -0400, Jeff Mahoney wrote:
> Ric's right about disk drives, though. They'll remap the bad sectors
> automatically at the hardware level. When you start to see bad sectors
> at the file system level, it means that the sectors reserved for
> remapping have been exhausted and you should replace the disk.
There are a couple of cases where you can see bad block errors on a good
drive.
If a block is written with a bad CRC for some reason...the write head
got a freak blip or it lost power as it was writing, or the data went
corrupt while sitting on disk, then it will read as a bad block, but
rewriting would fix it.
A RAID media verify or a badblocks -n run can usually fix these.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-04-04 0:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 5:03 bad block management kgp
2008-04-01 18:55 ` Christian Kujau
2008-04-01 19:32 ` Ric Wheeler
2008-04-01 19:51 ` Jeff Mahoney
2008-04-01 22:11 ` Edward Shishkin
2008-04-02 4:50 ` jyotiv
2008-04-02 10:43 ` Ric Wheeler
2008-04-02 11:22 ` jyotiv
2008-04-02 13:31 ` Ric Wheeler
2008-04-02 13:14 ` Jeff Mahoney
2008-04-04 0:14 ` Zan Lynx [this message]
2008-04-04 4:21 ` Toby Thain
2008-04-04 16:12 ` Zan Lynx
2008-04-04 22:41 ` Toby Thain
2008-04-04 18:58 ` Ric Wheeler
2008-04-04 22:42 ` Toby Thain
2008-04-05 12:31 ` Ric Wheeler
2008-04-05 14:07 ` Toby Thain
2008-04-05 15:08 ` Ric Wheeler
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=1207268072.379391.7.camel@localhost \
--to=zlynx@acm.org \
--cc=jeffm@suse.com \
--cc=jyotiv@tataelxsi.co.in \
--cc=lists@nerdbynature.de \
--cc=reiserfs-devel@vger.kernel.org \
--cc=ric@emc.com \
/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.