On Thu, Sep 22, 2011 at 10:12:12AM -0400, Josef Bacik wrote:
> Well that is from the tree logging code, so give this a whirl.  It's
> going to dump a lot of info so make sure you capture everything before
> the --- cut here --- line.  Thanks,

The patch doesn't apply cleanly to the latest git (since my laptop
doesn't boot anymore, I'm using a different host to compile this) but it
was simple enough to patch manually.  Right now I'm on v3.1-rc7-d93dc5c.

I'm compiling at the moment, so bear with me! :-)

My patch looks like this:
--- fs/btrfs/free-space-cache.c.orig    2011-09-22 11:51:46.442129324 +0200
+++ fs/btrfs/free-space-cache.c 2011-09-22 17:11:46.715162968 +0200
@@ -381,6 +381,8 @@ int __load_free_space_cache(struct btrfs
                        }
 
                        if (entry->type == BTRFS_FREE_SPACE_EXTENT) {
+                               printk(KERN_ERR "adding extent [%llu-%llu]\n",
+                                       e->offset, e->bytes);
                                spin_lock(&ctl->tree_lock);
                                ret = link_free_space(ctl, e);
                                spin_unlock(&ctl->tree_lock);
@@ -402,6 +404,8 @@ int __load_free_space_cache(struct btrfs
                                        page_cache_release(page);
                                        goto free_cache;
                                }
+                               printk(KERN_ERR "adding bitmap [%llu-%llu]\n",
+                                       e->offset, e->bytes);
                                spin_lock(&ctl->tree_lock);
                                ret = link_free_space(ctl, e);
                                ctl->total_bitmaps++;

-- 
Mathieu Chouquet-Stringer                         math...@csetco.com
            The sun itself sees not till heaven clears.
                     -- William Shakespeare --
--
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

Reply via email to