From: Marc MERLIN <marc@merlins.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs unmountable, any btrfs tool segfaults
Date: Sat, 23 Aug 2014 20:07:12 -0700 [thread overview]
Message-ID: <20140824030712.GP3875@merlins.org> (raw)
In-Reply-To: <pan$cd143$1f075140$a44693a2$c17a5577@cox.net>
On Sun, Aug 24, 2014 at 01:21:17AM +0000, Duncan wrote:
> It used to be common courtesy to read a couple weeks of the the backgroup/
> backlist before posting questions as they might be answered already. I
> guess it isn't so these days...
This is not scalable. There shouldn't be any recovery wisdom that is
only in the mailing list archive. This should be copied to the wiki.
I've been doing my part (and then some :), so have others ), so I urge
the rest to update the wiki with important information likely to be
useful to others later.
> Anyway, see the second half of the following post (the first half is a
> different problem and solution) dealing with using restore with btrfs-
> find-root and etc, along with the wiki link mentioned (and of course the
> manpages as well). With some luck you can still get btrfs restore
> working. It worked for me recently (as you can see there, I had backups
> but they weren't as current as I would have liked).
>
> http://permalink.gmane.org/gmane.comp.file-systems.btrfs/37980
Please put this in the wiki :)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-08-24 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 16:39 btrfs unmountable, any btrfs tool segfaults Nikolay Shtabel
2014-08-24 1:21 ` Duncan
2014-08-24 3:07 ` Marc MERLIN [this message]
2014-08-24 15:48 ` Nikolay Shtabel
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=20140824030712.GP3875@merlins.org \
--to=marc@merlins.org \
--cc=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 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).