From: Jeff Mahoney <jeffm@suse.de>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: read error: how to fix?
Date: Fri, 14 Oct 2011 15:47:08 -0400 [thread overview]
Message-ID: <4E9891BC.5070802@suse.de> (raw)
In-Reply-To: <Bv$GAecT1uB@helmut.hullen.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/10/2011 11:58 AM, Helmut Hullen wrote:
> Hallo, Jeff,
>
> Du meintest am 10.10.11:
>
>>>>> Oct 7 18:16:55 Arktur kernel: ata5.00: exception Emask
>>>>> 0x0 SAct 0x0 SErr 0x0 action 0x0
>
> [...]
>
>>> I've just worked again with the 2 unreadable files.
>>>
>>> Copying them to another partition stopped somewhere, one
>>> time/file at about 98%, the other time at about 2%.
>
> [...]
>
>> I'd try replacing the SATA cable and if that doesn't fix it up,
>> you may be out of luck.
>
> There are 2 unreadable sectors (reproducable). Changing or
> re-mounting the cables doesn't help.
>
>> The thing is that marking sectors bad is a (pretty poor) band-aid
>> for a much bigger problem: If you're hitting persistent read
>> errors and re-writing the blocks doesn't fix it, your disk is
>> already close to being completely kaput and no amount of software
>> is going to help with that.
>
> The next steps could be:
>
> - adding a new 2-TByte disk (now there are 3 2-TByte disks) -
> balancing - removing the bad 2-TByte disk
>
> But I'm afraid when I run balancing then the bad sectors damage big
> parts of the contents. I've had such bad luck about 1 year ago,
> losing about 2 TByte of data (ok - I had a kind of backup in a
> neighbout town). I don't like to reproduce this experience.
>
> I'm afraid I have to buy 3 (or 4) 2-TByte disks, building them as a
> new raid0-data cluster and copy the complete contents from the old
> cluster to the new one. Doesn't sound good.
>
> -----------------------
>
> 2 bad sectors from a total of 4*10^9 sectors is (in another point
> of view) no bad error rate ...
Well, it's worse than that. The disk will try to correct for bad
sectors itself internally and will remap them. By the time you start
to see bad sectors on disk (where writing and then reading fails), the
disk's internal remap table has been filled. That hides the true
defect rate but it also means that it's only a matter of time before
you get more bad sectors.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6YkbwACgkQLPWxlyuTD7LrTACeJFBbYZtJrUVBwDM8+R2BBrHS
moIAn3wIZd2Q9TEo8mUkAhVtdZnHgYdr
=hpBv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-10-14 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 16:51 read error: how to fix? Helmut Hullen
2011-10-10 11:48 ` David Sterba
2011-10-10 13:28 ` Helmut Hullen
2011-10-10 14:07 ` Jeff Mahoney
2011-10-10 15:58 ` Helmut Hullen
2011-10-14 19:47 ` Jeff Mahoney [this message]
2011-10-15 18:47 ` Martin Steigerwald
2011-10-15 19:59 ` Helmut Hullen
2011-10-16 19:32 ` Calvin Walton
2011-10-17 3:35 ` Helmut Hullen
2011-10-18 15:33 ` Helmut Hullen
2011-10-21 9:40 ` Helmut Hullen
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=4E9891BC.5070802@suse.de \
--to=jeffm@suse.de \
--cc=Hullen@t-online.de \
--cc=helmut@hullen.de \
--cc=linux-btrfs@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