From: Hugo Mills <hugo@carfax.org.uk>
To: Tomasz Torcz <tomek@pipebreaker.pl>, linux-btrfs@vger.kernel.org
Subject: Re: Old (almost 2 years) btrfs failed fs. Parent transid failure. Can it be fixed ?
Date: Mon, 29 Oct 2012 12:47:12 +0000 [thread overview]
Message-ID: <20121029124712.GF5042@carfax.org.uk> (raw)
In-Reply-To: <20121029123313.GA19012@mother.jarsat.pl>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On Mon, Oct 29, 2012 at 01:33:13PM +0100, Tomasz Torcz wrote:
> On Mon, Oct 29, 2012 at 01:22:59PM +0100, Tommy Jonsson wrote:
> > Hi, i have an old btrfs file-system that crashed on a power-failure
> > for about 2 years ago.
> >
> > i have clone the
> > git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
> > (at 2012-10-29) and compiled the tools.
>
> I think you need to get branch "dangerdonoteveruse" to get real fsck code.
That's a very outdated piece of advice. That code is now in
mainline btrfs-progs, and has been since March. Tommy has the correct
and up-to-date version of the progs.
> > sudo mount -t btrfs /dev/sda /mnt/disk/
>
> Could you try with "-o recovery"?
That's worth a try as a first step.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- The last man on Earth sat in a room. Suddenly, there was a ---
knock at the door.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-10-29 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 12:22 Old (almost 2 years) btrfs failed fs. Parent transid failure. Can it be fixed ? Tommy Jonsson
2012-10-29 12:33 ` Tomasz Torcz
2012-10-29 12:47 ` Hugo Mills [this message]
2012-10-29 13:10 ` Tommy Jonsson
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=20121029124712.GF5042@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=tomek@pipebreaker.pl \
/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).