From: Arne Jansen <sensille@gmx.net>
To: "Marco L. Crociani" <marco.crociani@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to handle badblocks with btrfs?
Date: Tue, 28 Jun 2011 13:14:39 +0200 [thread overview]
Message-ID: <4E09B79F.70703@gmx.net> (raw)
In-Reply-To: <BANLkTinrJV8DApCp8R=MnN-UZdPe6OrujA@mail.gmail.com>
On 28.06.2011 01:36, Marco L. Crociani wrote:
> # smartctl -d ata -l selftest /dev/sda
> smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
> Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
>
> === START OF READ SMART DATA SECTION ===
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining
> LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed: read failure 90% 171
> 494581664
>
>
> What should I do to repair the disk?
Scrub can repair bad blocks as long as there's a good copy. To use scrub
you'll need the most recent rc-kernel and a btrfs-utility that supports
scrub, e.g. from the integration branch of Hugo Mills git tree, see his
recent mail for this.
> Is it possible to know which file is affected by the badblock?
There's a patch from Jan Schmidt for this, but it's not yet integrated.
>
> I found http://smartmontools.sourceforge.net/badblockhowto.html but is
> about to ext2/3/4 fs.
>
> I am concerned about the absence of fsck tool. Should I run badblocks
> on the unmounted fs?
> Thanks,
>
prev parent reply other threads:[~2011-06-28 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 23:36 How to handle badblocks with btrfs? Marco L. Crociani
2011-06-28 11:14 ` Arne Jansen [this message]
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=4E09B79F.70703@gmx.net \
--to=sensille@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=marco.crociani@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).