From: "A. James Lewis" <james@fsck.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Corrupt filesystem after power failure
Date: Thu, 10 Feb 2011 12:37:55 +0000 [thread overview]
Message-ID: <1297341475.32582.688.camel@cheyenne> (raw)
In-Reply-To: <AANLkTikujRv82iNQ4vNvyGGqDotH_bOxfFCqqnC0ycU2@mail.gmail.com>
I'm far from an expert here, but perhaps you would be worth trying a
newer version of the BTRFS drivers, either via a newer kernel or
re-compiling a kernel with updated BTRFS patches.
I would think that the simplest "quick test" to see if this would help
you would be to get a snapshot from Ubuntu's "daily build" live CD iso,
and try mounting the filesystem with that... since it will have a recent
RC of 2.6.38 kernel which has a much more recent BTRFS version than the
2.6.34 which you are using.
http://cdimage.ubuntu.com/daily-live/current/
YMMV, but it's certainly something else to try.
James.
On Thu, 2011-02-10 at 22:29 +1100, Anil Kumar wrote:
> Hi,
> I am using btrfs on my /home successfully for a while now.
> After a power failure I am no longer able to mount it. I tried to use
> btrfsck without any success.
> The backup I have is about a month old, is there a way I can salvage my files?.
> Full backtrace is at http://pastebin.com/4Re7tVFP
> I am aware of the danger of dataloss and wanted to change the filesystem.
> Anyway it's too late now
>
> Anil
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-10 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 11:29 Corrupt filesystem after power failure Anil Kumar
2011-02-10 12:37 ` A. James Lewis [this message]
2011-02-10 12:57 ` Hugo Mills
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=1297341475.32582.688.camel@cheyenne \
--to=james@fsck.co.uk \
--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).