linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Sascha Biermanns <saschakb@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: at fs/btrfs/extent-tree.c:5695 btrfs_alloc_free_block+0x22c/0x370 [btrfs]()
Date: Tue, 31 May 2011 04:18:33 -0400	[thread overview]
Message-ID: <1306829753-sup-916@shiny> (raw)
In-Reply-To: <4DE4A30A.9010207@gmail.com>

Excerpts from Sascha Biermanns's message of 2011-05-31 04:12:58 -0400:
> Yesterday, I compiled the new kernel 3.0rc1 from git, but I never
> successed to go over the point: "Removing old temporary files".
> Pressing control-c let me boot on, but the pc was the complete time on
> very high load. It took me minutes, just to reach the tty login - and
> again minutes after login in, that I had my shell and a prompt to enter
> something. The load was at that time beyond 10.
> 
> Now in my /var/log/messages, I found the following warning - and because
> it happens when "removing" temporary/old files, that might be why the
> computer has so much trouble:
> 

> May 30 23:25:17 localhost kernel: [17117.213589] Call Trace:

Do you have the very first full oops?  This has the call trace, but not
the beginning text that describes why we've crashed.

-chris

  reply	other threads:[~2011-05-31  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  8:12 WARNING: at fs/btrfs/extent-tree.c:5695 btrfs_alloc_free_block+0x22c/0x370 [btrfs]() Sascha Biermanns
2011-05-31  8:18 ` Chris Mason [this message]
2011-05-31  8:30   ` Sascha Biermanns

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=1306829753-sup-916@shiny \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=saschakb@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).