UBIFS: print useful debugging messages when cannot recover gc_lnum
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
Tue, 26 Apr 2011 07:17:00 +0000 (10:17 +0300)
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
Fri, 13 May 2011 16:23:56 +0000 (19:23 +0300)
If we fail to recover the gc_lnum we just return an error and it then
it is difficult to figure out why this happened. This patch adds useful
debugging information which should make it easier to debug the failure.

Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
fs/ubifs/recovery.c

index 3e0eedbe49ce064a44185bc3d214b2710b1c5b9f..3d2598deaa58cf5716aa335f502822921f0158d2 100644 (file)
@@ -1177,6 +1177,8 @@ find_free:
        lnum = ubifs_find_free_leb_for_idx(c);
        if (lnum < 0) {
                dbg_err("could not find an empty LEB");
+               dbg_dump_lprops(c);
+               dbg_dump_budg(c, &c->bi);
                return lnum;
        }
        /* And reset the index flag */
This page took 0.025098 seconds and 5 git commands to generate.