From: Ravi Pinjala <ravi@p-static.net>
To: linux-btrfs@vger.kernel.org
Subject: Replacing corrupted files/directories
Date: Thu, 2 Dec 2010 19:25:09 -0800 [thread overview]
Message-ID: <AANLkTimKQ17g7hZrS0-AVxCyhyaLumWCa11Aq1vf+c9_@mail.gmail.com> (raw)
Is there a recommended way to replace a corrupted file or directory on
btrfs? The use case I'm thinking of is handling filesystem corruption
by restoring only the corrupted files from backup. For a corrupted
file, it seems like deleting the file and replacing it with the copy
from the backup works, but I don't know if this is necessarily the
best way - the nature of copy-on-write means that there's still
corrupt data lying around on the filesystem, right? And for
directories, it's tricky, because (afaik) there's no way to delete a
directory without first walking it; not good if it's corrupted.
I think this is probably also relevant to something like Ceph or CRFS,
where redundancy exists, but isn't managed by btrfs directly.
reply other threads:[~2010-12-03 3:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTimKQ17g7hZrS0-AVxCyhyaLumWCa11Aq1vf+c9_@mail.gmail.com \
--to=ravi@p-static.net \
--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).