All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Chouquet-Stringer <mathieu@csetco.com>
To: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Cc: David Sterba <dave@jikos.cz>
Subject: Re: Btrfs bug with g38867a2 and a question
Date: Thu, 22 Sep 2011 12:13:44 +0200	[thread overview]
Message-ID: <20110922101344.GA13667@kashmir> (raw)
In-Reply-To: <20110921231055.GN22205@twin.jikos.cz>

On Thu, Sep 22, 2011 at 01:10:55AM +0200, David Sterba wrote:
> please prefix printk messages with "btrfs: "

Well my computer crashed before I could reboot with the newly compiled
kernel.  And now it bugs while it tries to mount the kernel meaning my
computer is fscked! :-)

Bug at fs/btrfs/free-space-cache.c:1327

(I have a screenshot if needed)

function remove_from_bitmap

        /*
         * XXX - this can go away after a few releases.
         *
         * since the only user of btrfs_remove_free_space is the tree logging
         * stuff, and the only way to test that is under crash conditions, we
         * want to have this debug stuff here just in case somethings not
         * working.  Search the bitmap for the space we are trying to use to
         * make sure its actually there.  If its not there then we need to stop
         * because something has gone wrong.
         */
        search_start = *offset;
        search_bytes = *bytes;
        search_bytes = min(search_bytes, end - search_start + 1);
        ret = search_bitmap(ctl, bitmap_info, &search_start, &search_bytes);
===>    BUG_ON(ret < 0 || search_start != *offset);

So question is now: how do I recover from this? :-)

-- 
Mathieu Chouquet-Stringer                         mathieu@csetco.com
            The sun itself sees not till heaven clears.
	             -- William Shakespeare --

  reply	other threads:[~2011-09-22 10:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 18:53 Btrfs bug with g38867a2 and a question Mathieu Chouquet-Stringer
2011-09-21 20:18 ` Josef Bacik
2011-09-21 20:35   ` Mathieu Chouquet-Stringer
2011-09-21 23:10   ` David Sterba
2011-09-22 10:13     ` Mathieu Chouquet-Stringer [this message]
2011-09-22 11:05       ` David Sterba
2011-09-22 11:35         ` Mathieu Chouquet-Stringer
     [not found]     ` <CALiWzOg8CQJF7OfMex1uJTa+doDZ8oufV1nAbos99Z4ev-+xKg@mail.gmail.com>
2011-09-22 14:12       ` Josef Bacik
2011-09-22 15:16         ` Mathieu Chouquet-Stringer
2011-09-22 18:22         ` Mathieu Chouquet-Stringer
2011-09-22 19:00           ` Josef Bacik
2011-09-22 19:30             ` Mathieu Chouquet-Stringer
2011-09-22 20:32               ` Mathieu Chouquet-Stringer
2011-09-23 12:55                 ` Mathieu Chouquet-Stringer
2011-09-23 14:49                   ` Josef Bacik
2011-09-23 15:31                     ` Mathieu Chouquet-Stringer
2011-09-23 15:34                       ` Josef Bacik
2011-09-23 17:16                         ` Mathieu Chouquet-Stringer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110922101344.GA13667@kashmir \
    --to=mathieu@csetco.com \
    --cc=dave@jikos.cz \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.