On Thu, Apr 7, 2011 at 9:44 AM, Jordan Patterson <jordanp@xxxxxxxxx> wrote: > On Thu, Apr 7, 2011 at 7:17 AM, Josef Bacik <josef@xxxxxxxxxx> wrote: >> On Wed, Apr 06, 2011 at 02:47:28PM -0600, Jordan Patterson wrote: >>> Hi Josef: >>> >>> I tried your latest patch, since I had the same issue from the first >>> email. With the patch applied, I am now hitting the >>> BUG_ON(block_group->total_bitmaps >= max_bitmaps); in add_new_bitmap >>> in >>> fs/btrfs/free-space-cache.c:1246 as soon as I mount the filesystem, >>> with or without -o clear_cache. >>> >>> It works fine in 2.6.38. I get the same error after mounting with >>> clear_cache under 2.6.38 and rebooting into the current kernel with >>> your patch. >>> >> >> Do you have a backtrace so I can see how we're getting here? This is a seperate >> issue from the one this patch tries to solve, but now that it seems that's fixed >> I will work on this now :). Thanks, >> >> Josef >> > > I wasn't able to test until now, but Johannes' suggestion may have > fixed the issue for me. I added clear_cache to my rootflags in grub, > and it is now mounted fine with the current btrfs code with your last > patch. I don't have the backtrace, but I'll send it to you it if I > see it happen again. > > Thanks. > > Jordan > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
