From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: "Frédéric COIFFIER" <frederic.coiffier@free.fr>
Subject: Re: How to recover uncorrectable errors ?
Date: Sat, 16 Mar 2013 19:19:41 +0100 [thread overview]
Message-ID: <201303161919.41734.Martin@lichtvoll.de> (raw)
In-Reply-To: <6033676.gK0GbPgrpE@athlonxp>
Am Freitag, 8. März 2013 schrieb Frédéric COIFFIER:
> Today, I can't remove the file (and I can't delete its directory),
> updatedb runs during hours when it tries to read this file. So, what is
> the best way to recover these errors (as I think that some files are
> definitely lost) ? I would like to identify the corrupted files and to
> delete them.
Well, if nothing else works, you can still make a backup, diff it with an
older backup to possible recover the corrupted files or at least older
versions of it and redo the filesystem. After verify that the hardware
works okay :)
As said, these errors are called uncorrectable for a reason. When they
happen on file data it should be possible to delete the offending file,
but then AFAIK BTRFS also reports on which file they happen.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
prev parent reply other threads:[~2013-03-16 18:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 8:54 How to recover uncorrectable errors ? Frédéric COIFFIER
2013-03-13 8:10 ` Frédéric COIFFIER
2013-03-16 18:16 ` Martin Steigerwald
2013-03-20 13:33 ` Frédéric COIFFIER
2013-03-20 18:19 ` Chris Murphy
2013-03-20 19:24 ` Roman Mamedov
2013-03-20 20:17 ` Chris Murphy
2013-03-21 8:57 ` Frédéric COIFFIER
2013-03-21 15:09 ` Chris Murphy
2013-03-20 18:59 ` Martin Steigerwald
2013-03-20 19:06 ` cwillu
2013-03-21 8:36 ` Frédéric COIFFIER
2013-03-21 13:27 ` Martin Steigerwald
2013-03-16 18:19 ` Martin Steigerwald [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=201303161919.41734.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=frederic.coiffier@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).