From: Sylvain Joyeux <sylvain.joyeux@m4x.org>
To: linux-btrfs@vger.kernel.org
Subject: Replace a corrupted block using a known-good file from another filesystem ?
Date: Tue, 5 Jan 2016 10:25:36 -0200 [thread overview]
Message-ID: <CAFENT7KXjVBa0n16=FuWhK6xvgFZ7N5GdH_dVufaZbsx9wmeNA@mail.gmail.com> (raw)
In the course of the few btrfs crashes I had on my USB backup drive
(NOT the drive from my other bug report, which is an internal SATA
drive) - in the last 6 months or so - I ended up having a 4 to 5 bad
checksums reported by scrub.
This drive is used to synchronize snapshots from my main machine, and
the corrupted files are system files that are still present on the
main machine.
I could obviously reset the filesystem on the USB drive, but since the
goal is to keep a backup history (which the main machine does not
keep), I would rather avoid that.
Would there be a way to replace the bad blocks using the good file on
the main filesystem ? Replacing it in each snapshot separately does
not look very appealing as the file is present on most of them.
Sylvain
next reply other threads:[~2016-01-05 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 12:25 Sylvain Joyeux [this message]
2016-01-05 12:37 ` Replace a corrupted block using a known-good file from another filesystem ? Austin S. Hemmelgarn
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='CAFENT7KXjVBa0n16=FuWhK6xvgFZ7N5GdH_dVufaZbsx9wmeNA@mail.gmail.com' \
--to=sylvain.joyeux@m4x.org \
--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).