From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Accidental formatting
Date: Mon, 06 Feb 2012 08:40:52 +0100 [thread overview]
Message-ID: <5pc409-hou.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 4F2F4BF9.7070609@gmail.com
Fahrzin Hemmati <fahhem2@gmail.com> schrieb:
> I recently re-installed Ubuntu, and somewhere along the way the
> installer decided to clear out /var, which happens to be a separate
> btrfs device from /. When I do "btfrs filesystem df /var" it outputs this:
>
> Data: total=134.01GB, used=485.78
> System, DUP: total=8.00MB, used=20.00KB
> System: total=4.00MB, used=0.00
> Metadata, DUP: total=1.62GB, used=6.87MB
> Metadata: total=8.00MB, used=0.00
>
> The reserved Data, 134GB, resembles closely the amount of data on my
> drive before the formatting. Therefore, I believe what happened was the
> installer didn't format /var, just cleared out the files. I didn't
> properly backup /var, but I have important files on it. Is there a way
> to have btrfs look around the reserved metadata area for orphaned files
> and get them back?
I'd try "photorec" on this although I believe it will be hard for photorec
to recover the files due to btrfs' COW behaviour.
You could also try Josef's rescue tool or trying to intentionally corrupt
you current tree root so you could use "mount -o recovery" to let btrfs
mount an older tree root. This is just an idea, I think the btrfs folks here
have better ideas how to accomplish mounting an older tree root.
HTH
Kai
next prev parent reply other threads:[~2012-02-06 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 3:41 Accidental formatting Fahrzin Hemmati
2012-02-06 7:40 ` Kai Krakow [this message]
[not found] ` <CAD8hrTPmcuac6wtJPR=pHES1gQJ2Q+ft8OmNOOKopMQKmV+8qA@mail.gmail.com>
2012-02-06 8:42 ` Kai Krakow
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=5pc409-hou.ln1@hurikhan.ath.cx \
--to=hurikhan77+btrfs@gmail.com \
--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).