From: Josef Bacik <jbacik@fusionio.com>
To: "Szőts Ákos" <szotsaki@gmail.com>
Cc: Josef Bacik <JBacik@fusionio.com>,
"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 16:52:12 -0400 [thread overview]
Message-ID: <20130327205212.GM28030@localhost.localdomain> (raw)
In-Reply-To: <CAAr69zaQ22_SLg4sfUkDE=NBNTAUaSr9ZgaL=sTPJ-kvXkFRug@mail.gmail.com>
On Wed, Mar 27, 2013 at 01:17:56PM -0600, Szőts Ákos wrote:
> I ran two different versions of btrfsck on the partition.
>
> The first one was shipped with openSUSE 12.3, kernel 3.7.
> This is the original tool with which the partition was checked:
> http://paste.opensuse.org/74569620
>
> The second one is from your tree (maybe it's newer):
> http://filebin.ca/bfbwJezYwCV/btrfsck-v2.txt
>
BTW if the fsck doesn't fix your problem don't despair, I'm hacking up another
option for btrfs-image to just walk the trees themselves and scrape everything
so I can have a full image from you and then I'll be able to fix fsck to fix
your file system. Thanks,
Josef
next prev parent reply other threads:[~2013-03-27 20:52 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
2013-03-27 19:17 ` Szőts Ákos
2013-03-27 20:39 ` Josef Bacik
2013-03-27 20:52 ` Josef Bacik [this message]
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=20130327205212.GM28030@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.