From: Josef Bacik <jbacik@fusionio.com>
To: "Szőts Ákos" <szotsaki@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel bug on mismatching generation_v2 in inode.c:835
Date: Wed, 27 Mar 2013 14:33:25 -0400 [thread overview]
Message-ID: <20130327183325.GK28030@localhost.localdomain> (raw)
In-Reply-To: <CAAr69zZ7OpGpT7qcKdWA0k_0MR-wbhd-+EFGBQ+TQ5CycM8GDg@mail.gmail.com>
On Tue, Mar 26, 2013 at 08:33:27AM -0600, Szőts Ákos wrote:
> Dear list members,
>
> In my previous thread at
> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg23333.html
> there was a space_cache kernel bug/panic on kernel 3.8. I could
> successfully "fix" that with rebuilding the cache. But some files were
> missing/corrupted. So I booted a rescue CD with kernel 3.7 and ran
> btrfsck --repair, which repaired quite a few things.
>
> After a reboot I got the following message:
> [ 469.457386] btrfs: disk space caching is enabled
> [ 469.503612] btrfs: mismatching generation and generation_v2 found
> in root item. This root was probably mounted with an older kernel.
> Resetting all new fields.
>
> As soon as anything had wanted to read a bit from the file system, the
> hard drive went crazy and was working for 5-10 minutes. After I got a
> kernel panic which said there's an error in fs/btrfs/inode.c:835.
>
> In the moment I don't just mount, but want to read something from the
> mounted file system under the rescue system, the same procedure
> happens.
>
> I made some pictures of it (since I cannot read anything from the
> logs, if there are any).
> You can find them here: www.morrohun.hu/temp/btrfs/v2/[123].jpg
>
> I wanted to create an image with the aforementined btrfs-image tool,
> but yet to have any success .
>
> Could you please give me an advice what can I do now? Living on a
> live-CD is not a life insurance :)
>
Can you run btrfsck without --repair and capture the output and upload it
somewhere so I can make sure I've restored properly. I can reproduce the
problem but I'm worried that I'm reproducing it because I've restored badly and
there's something else wrong, I want to make sure I'm seeing exactly what you
are seeing. Thanks,
Josef
next prev parent reply other threads:[~2013-03-27 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 14:33 Kernel bug on mismatching generation_v2 in inode.c:835 Szőts Ákos
2013-03-26 14:48 ` Josef Bacik
2013-03-26 15:59 ` Szőts Ákos
2013-03-26 17:34 ` Josef Bacik
2013-03-26 18:17 ` Josef Bacik
2013-03-26 18:25 ` Szőts Ákos
2013-03-26 18:47 ` Josef Bacik
2013-03-27 11:51 ` Szőts Ákos
2013-03-27 12:49 ` Josef Bacik
2013-03-27 13:58 ` Josef Bacik
2013-03-27 13:59 ` Szőts Ákos
2013-03-27 18:33 ` Josef Bacik [this message]
2013-03-27 19:17 ` Szőts Ákos
2013-03-27 20:39 ` Josef Bacik
2013-03-27 20:52 ` Josef Bacik
2013-03-27 21:42 ` Szőts Ákos
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=20130327183325.GK28030@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=szotsaki@gmail.com \
/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