From: Hugo Mills <hugo@carfax.org.uk>
To: Avi Kivity <avi.kivity@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Suddenly, a dead filesystem
Date: Tue, 23 Aug 2011 15:28:07 +0100 [thread overview]
Message-ID: <20110823142807.GC4172@carfax.org.uk> (raw)
In-Reply-To: <20110823142727.GB4172@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]
On Tue, Aug 23, 2011 at 03:27:27PM +0100, Hugo Mills wrote:
> On Tue, Aug 23, 2011 at 05:15:46PM +0300, Avi Kivity wrote:
> > I've been using btrfs for a while as my /home (converted from ext4;
> > encrypted lvm) when it died on me. Mounting it crashes immediately,
> > here's a log:
> [...]
> > [ 6.456117] Call Trace:
> > [ 6.456117] [<ffffffffa005646e>] add_inode_ref+0x2e6/0x37c [btrfs]
> > [ 6.456117] [<ffffffffa00493f6>] ? read_extent_buffer+0xc3/0xe3 [btrfs]
> > [ 6.456117] [<ffffffffa0056e14>] replay_one_buffer+0x197/0x212 [btrfs]
> > [ 6.456117] [<ffffffffa0054e94>] walk_down_log_tree+0x15a/0x2c1 [btrfs]
> > [ 6.456117] [<ffffffffa005507a>] walk_log_tree+0x7f/0x19e [btrfs]
> > [ 6.456117] [<ffffffff8123a8d9>] ? radix_tree_lookup+0xb/0xd
> > [ 6.456117] [<ffffffffa0058148>] btrfs_recover_log_trees+0x28b/0x298 [btrfs]
> > [ 6.456117] [<ffffffffa0056c7d>] ? replay_one_dir_item+0xbd/0xbd [btrfs]
> > [ 6.456117] [<ffffffffa002a192>] open_ctree+0x10f1/0x13ff [btrfs]
> [...]
> > Tried btrfsck, immediate segfault.
>
> Yes, it does that,I'm afraid. (It also doesn't fix anything).
>
> > Both kernel and btrfsprogs are stock Fedora 15. I still have the
> > logical volume and would like to recover it. Its fairly easy to try
> > out things in a virtual machine, so if you have a patch you want me to
> > try out, I'm here.
>
> It looks like you've got a corrupt log tree. The quick and easy fix
> for that is on the wiki in the problem FAQ page [1].
... or use Josef's fix first. :)
H.
> Could you give a bit more information about what happened in the
> crash immediately prior to the FS being unmountable, and how your
> storage is configured?
>
> Hugo.
>
> [1] https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can.27t_mount_my_filesystem.2C_and_I_get_a_kernel_oops.21
>
--
=== 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
--- You stay in the theatre because you're afraid of having no ---
money? There's irony...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-08-23 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 14:15 Suddenly, a dead filesystem Avi Kivity
2011-08-23 14:23 ` Josef Bacik
2011-08-23 21:08 ` Avi Kivity
2011-09-30 21:40 ` Avi Kivity
2011-10-03 14:34 ` Josef Bacik
2011-10-03 15:12 ` Avi Kivity
2011-10-03 18:07 ` Avi Kivity
2011-10-04 14:39 ` Avi Kivity
2011-10-04 19:40 ` Avi Kivity
2011-10-04 19:41 ` Josef Bacik
2011-10-04 19:50 ` Avi Kivity
2011-10-04 20:01 ` Josef Bacik
2011-10-04 20:06 ` Avi Kivity
2011-08-23 14:27 ` Hugo Mills
2011-08-23 14:28 ` Hugo Mills [this message]
2011-08-23 22:22 ` Avi Kivity
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=20110823142807.GC4172@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=avi.kivity@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