public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Marc Schoechlin <linux-btrfs@vger.kernel.org>
Subject: Re: BUG: Bonnie++ stresstest with parallel balanceing chunks across all devices
Date: Fri, 27 Feb 2009 00:06:02 +0300	[thread overview]
Message-ID: <20090226210602.GB6215@ioremap.net> (raw)
In-Reply-To: <20090226203608.GB4024@256bit.org>

On Thu, Feb 26, 2009 at 09:36:08PM +0100, Marc Schoechlin (linux-btrfs@vger.kernel.org) wrote:
> [  359.658789] btrfs allocation failed flags 68, wanted 4096
> [  359.659966] space_info has 932491264 free, is full
> [  359.660007] block group 14802485248 has 936378368 bytes, 3522560 used 364544 pinned 0 reserved
> [  359.660076] 87 blocks of free space at or bigger than bytes is
> [  359.660226] ------------[ cut here ]------------
> [  359.660273] kernel BUG at fs/btrfs/extent-tree.c:3190!

Looks like a no-space-left feature.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2009-02-26 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 20:36 BUG: Bonnie++ stresstest with parallel balanceing chunks across all devices Marc Schoechlin
2009-02-26 21:06 ` Evgeniy Polyakov [this message]
2009-02-27 15:39 ` Josef Bacik

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=20090226210602.GB6215@ioremap.net \
    --to=zbr@ioremap.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox