Re: btrfs: Error removing orphan entry, stopping orphan cleanup. could not do orphan cleanup -22
On Fri, Feb 08, 2013 at 11:36:48AM -0700, Marguerite Su wrote: On Wed, Feb 6, 2013 at 11:15 PM, Josef Bacik jba...@fusionio.commailto:jba...@fusionio.com wrote: Btrfs-next is based on 3.7, you should be able to just git diff v3.7.. whatever.patch and get all the changes you need. Thanks, Hi, Josef, Sorry to bother you again. I tried for days and asked some of my friends, but I'm still confused about what you want me to do and how to do... I check the #btrfs-next[1], its latest tag is v3.4-rc2 and there's only one master branch. There's no `v3.7` around there...So I'm confused about what you meant. Can you be more detailed ? I know I need a diff...but how...and which repo should I apply it on? my /usr/src/linux or #btrfs-next itself? Thanks a lot Oh sorry I have the tags locally because I pull linus's tags onto my tree, but I don't push them out. So pull my tree (I just pushed another fix for this problem out yesterday so it definitely should be fixed) and just do git diff 29594404d7fe73cd80eaa4ee8c43dcc53970c60e.. btrfs.patch and that should work. Thanks, Josef -- 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: btrfs: Error removing orphan entry, stopping orphan cleanup. could not do orphan cleanup -22
On Wed, Feb 6, 2013 at 4:45 AM, Josef Bacik jba...@fusionio.com wrote: Ok so I think we've fixed this already, can you build btrfs-next and try mounting with that and see if it fixes the problem? Thanks, Hi, Josef, Is there any btrfs git compatible with kernel 3.7 and absorbs this fix? So I can dkms it, I'm using openSUSE 12.3 Beta1 with kernel 3.7, I can update to 3.8, but next time I do system update to RC1 it will fallback to 3.7 again. #btrfs-next seems to move forward to 3.8. /uapi/linux/btrfs.h doesn't exist in kernel 3.7, it still use the old ioctl.h, I tried to revert the ioctl.h btrfs.h patch, but there's still errors about: /usr/src/linux-3.7.1-1/include/trace/events/btrfs.h: In function ‘ftrace_raw_event_btrfs_transaction_commit’: /usr/src/linux-3.7.1-1/include/trace/events/btrfs.h:61:1: error: incompatible types when assigning to type ‘u64’ from type ‘atomic64_t’ Thanks Marguerite -- 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: btrfs: Error removing orphan entry, stopping orphan cleanup. could not do orphan cleanup -22
On Wed, Feb 06, 2013 at 06:03:14AM -0700, Marguerite Su wrote: On Wed, Feb 6, 2013 at 4:45 AM, Josef Bacik jba...@fusionio.com wrote: Ok so I think we've fixed this already, can you build btrfs-next and try mounting with that and see if it fixes the problem? Thanks, Hi, Josef, Is there any btrfs git compatible with kernel 3.7 and absorbs this fix? So I can dkms it, I'm using openSUSE 12.3 Beta1 with kernel 3.7, I can update to 3.8, but next time I do system update to RC1 it will fallback to 3.7 again. #btrfs-next seems to move forward to 3.8. /uapi/linux/btrfs.h doesn't exist in kernel 3.7, it still use the old ioctl.h, I tried to revert the ioctl.h btrfs.h patch, but there's still errors about: /usr/src/linux-3.7.1-1/include/trace/events/btrfs.h: In function ‘ftrace_raw_event_btrfs_transaction_commit’: /usr/src/linux-3.7.1-1/include/trace/events/btrfs.h:61:1: error: incompatible types when assigning to type ‘u64’ from type ‘atomic64_t’ Btrfs-next is based on 3.7, you should be able to just git diff v3.7.. whatever.patch and get all the changes you need. Thanks, Josef -- 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: btrfs: Error removing orphan entry, stopping orphan cleanup. could not do orphan cleanup -22
On Tue, Feb 05, 2013 at 12:27:04PM -0700, Marguerite Su wrote: Hi, I got a kernel crash or something said this. I see it attach a dump, so it seems btrfs devs are the only group who can read it... Eesh can you fpaste this, it got wrapped by your mailer and I can't read it. Thanks, Josef -- 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: btrfs: Error removing orphan entry, stopping orphan cleanup. could not do orphan cleanup -22
On Wed, Feb 6, 2013 at 3:35 AM, Josef Bacik jba...@fusionio.com wrote: Eesh can you fpaste this, it got wrapped by your mailer and I can't read it. Thanks, Hi, Josef, Of course, http://paste.opensuse.org/80508108 I at first thought pasting here may help archive. but Gmail sucks...sorry! Marguerite -- 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: btrfs: Error removing orphan entry, stopping orphan cleanup. could not do orphan cleanup -22
On Tue, Feb 05, 2013 at 01:37:50PM -0700, Marguerite Su wrote: On Wed, Feb 6, 2013 at 3:35 AM, Josef Bacik jba...@fusionio.com wrote: Eesh can you fpaste this, it got wrapped by your mailer and I can't read it. Thanks, Hi, Josef, Of course, http://paste.opensuse.org/80508108 I at first thought pasting here may help archive. but Gmail sucks...sorry! Ok so I think we've fixed this already, can you build btrfs-next and try mounting with that and see if it fixes the problem? Thanks, Josef -- 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
