From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: read error: how to fix?
Date: 18 Oct 2011 17:33:00 +0200 [thread overview]
Message-ID: <Bw4cYUfy1uB@helmut.hullen.de> (raw)
In-Reply-To: <1318793530.2588.28.camel@nayuki.kepstin.ca>
Hallo, Calvin,
Du meintest am 16.10.11:
[...]
> If you have pending sectors, causing the drive to reallocate them is
> very simple. Write data (any data) over the sector in question - the
> drive will then remap it onto the spare area to do the write. (The
> easiest way is to do something like dd if=/dev/zero of=/dev/sdX; but
> if you know the exact sector number, "hdparm --write-sector" can
> remap it quickly.)
I have to try in the next days ...
> Keep in mind, though - if you have a single reallocated sector on a
> drive, it means that the drive medium is deteriorating. It's very
> likely that you will have additional failures in the future,
> resulting in more IO errors and lost data. For your sanity, I
> recommend replacing a drive as soon as you see any one error on it.
Actually "dd if=/dev/sdg of=/dev/zero " tells (in "/var/log/warn")
strange things like
Oct 18 14:42:48 Arktur kernel: Buffer I/O error on device sdg, logical block 29792786
Oct 18 14:42:48 Arktur kernel: Buffer I/O error on device sdg, logical block 29792787
Oct 18 14:43:04 Arktur kernel: end_request: I/O error, dev sdg, sector 238342224
Oct 18 14:43:04 Arktur kernel: Buffer I/O error on device sdg, logical block 29792778
Oct 18 14:43:20 Arktur kernel: end_request: I/O error, dev sdg, sector 238342224
Oct 18 14:43:20 Arktur kernel: Buffer I/O error on device sdg, logical block 29792778
-------------------------
>From yesterday to this morning the number of offline uncorrectable has
grown from 25 to 26 - no good omen.
Maybe there are some files damaged - the disk is filled with about 1.4
TByte, it's part of a btrfs cluster with more than 4 TByte data.
What about "btrfsck" - can it help? Or may it lead to one more crash?
When I try to copy the whole cluster to another place (I had this
problem some days ago) then the system crashes when it tries to access
that special file that uses such a defect sector. When I can first
detect the name of this file and then exclude it from copying then "cp"
works.
Nice problems ...
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-10-18 15:33 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
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 [this message]
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=Bw4cYUfy1uB@helmut.hullen.de \
--to=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