From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: read error: how to fix?
Date: 07 Oct 2011 18:51:00 +0200 [thread overview]
Message-ID: <BvO7vnJy1uB@helmut.hullen.de> (raw)
Hallo,
I'm just copying about 1.5 TByte from a 3-disks-btrfs directory (data:
raid0) to another disk. And there seem to be 2 damaged files, they stop
the copying process.
Oct 7 18:16:55 Arktur kernel: ata5.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x0
Oct 7 18:16:55 Arktur kernel: ata5.00: BMDMA2 stat 0x80d2009
Oct 7 18:16:55 Arktur kernel: ata5.00: failed command: READ DMA
Oct 7 18:16:55 Arktur kernel: ata5.00: cmd c8/00:40:57:d0:34/00:00:00:00:00/ee tag 0 dma 32768 in
Oct 7 18:16:55 Arktur kernel: res 51/40:40:57:d0:34/00:03:0e:00:00/fe Emask 0x9 (media error)
Oct 7 18:16:55 Arktur kernel: ata5.00: status: { DRDY ERR }
Oct 7 18:16:55 Arktur kernel: ata5.00: error: { UNC }
Oct 7 18:16:55 Arktur kernel: ata5.00: configured for UDMA/100
Oct 7 18:16:55 Arktur kernel: ata5: EH complete
(repeating every 3 seconds)
The files contain no valuable data (*.mpeg files, reproducable). But how
can I tell the disk not to use the damaged sector(s)?
On an ext2/3 system I used "badblocks" - is there some comparable tool
for btrfs?
Viele Gruesse!
Helmut
next reply other threads:[~2011-10-07 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 16:51 Helmut Hullen [this message]
2011-10-10 11:48 ` read error: how to fix? 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
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=BvO7vnJy1uB@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