Linux Btrfs filesystem development
 help / color / mirror / Atom feed
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: Tue, 26 Mar 2013 14:17:13 -0400	[thread overview]
Message-ID: <20130326181713.GD28030@localhost.localdomain> (raw)
In-Reply-To: <CAAr69zbBXr_c1_xroqueHG0Zobo8H94a2p6kB+GTsZVfkFCtGg@mail.gmail.com>

On Tue, Mar 26, 2013 at 09:59:57AM -0600, Szőts Ákos wrote:
> The error was just a silly "permission denied" one.
> 
> I uploaded the created image to www.morrohun.hu/temp/btrfs/btrfs.img
> SHA1: 90ee61e0724700495d26678d58dc229e04a04cc4
> Please, write me when you downloaded and I'll delete it.
> 
> I have the idea to run btrfsck from your tree on the file system
> again, but I won't touch the fs until you said so :).
> 

You did take this image while the file system was unmounted right?  I'm seeing
different weirdness with the restored image, trying to figure out if it's a
problem with the restore or with the dump.  Thanks,

Josef

  parent reply	other threads:[~2013-03-26 18:17 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 [this message]
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
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=20130326181713.GD28030@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