From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs recovery: What do the commands actually do?
Date: Fri, 4 Oct 2013 18:32:38 +0000 (UTC) [thread overview]
Message-ID: <pan$605b6$d8682eff$c911a507$660aae64@cox.net> (raw)
In-Reply-To: l2mntu$416$1@ger.gmane.org
Martin posted on Fri, 04 Oct 2013 16:47:19 +0100 as "condensed":
> There's ad-hoc comment for various commands to recover from filesystem
> errors.
>
> But what do they actually do and when should what command be used?
> What do they do exactly and what are the indicators to try using them?
> Or when should you 'give up' on a filsystem and just retrieve whatever
> data can be read and start again?
>
> All that lot sounds good for a wiki page ;-)
I recognize your name so you're a regular poster and may well have seen
this recover steps/order post from Hugo Mills, but you didn't mention it,
so...
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/27999
As you suggest, that should really go in the wiki (maybe it's there
already since that post, I haven't actually checked recently, but your
post reads as if you looked and couldn't find a recovery list of this
nature), but I've not gotten around to creating an account for myself
there yet and committing it, and if no one else has either...
But I do have it bookmarked for posting here, and for the day I do create
myself that wiki account, if no one else has gotten to it by then...
And while that answers what and what order, it doesn't cover what the
commands actually do or why you'd /use/ that order, and that'd be very
good to add as well.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-10-04 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 15:47 btrfs recovery: What do the commands actually do? Martin
2013-10-04 18:32 ` Duncan [this message]
2013-10-04 18:54 ` Martin
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='pan$605b6$d8682eff$c911a507$660aae64@cox.net' \
--to=1i5t5.duncan@cox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.