Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Szőts Ákos
I ran btrfsck three times and tried to restart the OS. After a generation_v2 resetting it booted and now it works! :) Thank you very much for your help! Two btrfsck run was needed for the complete cleanup, but interestingly the end statistics were a little bit different each time. Specificall

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Josef Bacik
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 seco

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Josef Bacik
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 seco

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Szőts Ákos
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

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Josef Bacik
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/msg2.html > there was a space_cache kernel bug/panic on kernel 3.8. I could > successfully "fix" that with rebuilding the cach

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Szőts Ákos
Oh, that's a very good news! Thank you very much :) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Josef Bacik
On Wed, Mar 27, 2013 at 05:51:32AM -0600, Szőts Ákos wrote: > What do you think; is this issue in the file system can be repaired > with btrfsck? Or should I install a new, patched kernel on my > partition somehow? Ok I've successfully restored your image and I've reproduced your problem, I will l

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Josef Bacik
On Wed, Mar 27, 2013 at 05:51:32AM -0600, Szőts Ákos wrote: > What do you think; is this issue in the file system can be repaired > with btrfsck? Or should I install a new, patched kernel on my > partition somehow? Sorry I was flipping between your problem and somebody elses problem yesterday and

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-27 Thread Szőts Ákos
What do you think; is this issue in the file system can be repaired with btrfsck? Or should I install a new, patched kernel on my partition somehow? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-26 Thread Josef Bacik
On Tue, Mar 26, 2013 at 12:25:44PM -0600, Szőts Ákos wrote: > If my memory servers me well, it was taken in unmounted state. Do you > want me to take an other one and compare the SHA1 values? Nope I found the bug, just a problem with the restore. Thanks, Josef -- To unsubscribe from this list: s

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-26 Thread Szőts Ákos
If my memory servers me well, it was taken in unmounted state. Do you want me to take an other one and compare the SHA1 values? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-26 Thread Josef Bacik
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. >

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-26 Thread Josef Bacik
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. >

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-26 Thread Szőts Ákos
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,

Re: Kernel bug on mismatching generation_v2 in inode.c:835

2013-03-26 Thread Josef Bacik
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/msg2.html > there was a space_cache kernel bug/panic on kernel 3.8. I could > successfully "fix" that with rebuilding the cach