From: Chris Mason <chris.mason@oracle.com>
To: Frank Kingswood <frank@kingswood-consulting.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Warning and oops running bonnie
Date: Tue, 09 Sep 2008 06:35:35 -0400 [thread overview]
Message-ID: <1220956535.29741.29.camel@think.oraclecorp.com> (raw)
In-Reply-To: <ga580b$nhd$1@ger.gmane.org>
On Tue, 2008-09-09 at 08:18 +0100, Frank Kingswood wrote:
> Hallo!
>
> I was running bonnie to compare btrfs to alternatives, see where it is
> in terms of relative performance. It looks good (but has very high CPU
> usage, is that expected?), but then I get a warning and later an oops.
>
> This is using two >9GB partitions, and bonnie running with 3GB and later
> 9GB.
>
> kernel: Btrfs v0.16+417d87e57364 loaded
>
> Here begins the first run, mkfs -d raid0
>
> kernel: device label test devid 1 transid 7 /dev/sda2
> kernel: device label test devid 2 transid 7 /dev/sdb2
> kernel: device label test devid 1 transid 12 /dev/sda2
> kernel: space info full 9
>
> but it completes bonnie.
>
> Here begins the second run, mkfs -d raid1
>
> kernel: device label test devid 1 transid 7 /dev/sda2
> kernel: device label test devid 2 transid 7 /dev/sdb2
> kernel: device label test devid 1 transid 12 /dev/sda2
> kernel: space info full 17
> kernel: Unable to find block group for 9183821824
Well, you're hitting a variant of the enospc code. My guess is that
you've filled up the volume to the point where everything is allocated
as a data extent, then deleted the file to make room then tried run #2.
How big is the volume and how big are the files created by each run?
-chris
prev parent reply other threads:[~2008-09-09 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 7:18 Warning and oops running bonnie Frank Kingswood
2008-09-09 10:35 ` Chris Mason [this message]
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=1220956535.29741.29.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=frank@kingswood-consulting.co.uk \
--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