From: "Julian Andres Klode" <jak@jak-linux.org>
To: "Chris Mason" <chris.mason@oracle.com>
Cc: "Thomas Harning" <thomas.harning@trustbearer.com>,
linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG: kernel bug caught at 55% mark of portage cache update
Date: Fri, 19 Dec 2008 17:24:38 +0100 [thread overview]
Message-ID: <f0d609a70812190824o24b04d90j272476e149d6cff3@mail.gmail.com> (raw)
In-Reply-To: <1229703379.6695.18.camel@think.oraclecorp.com>
2008/12/19 Chris Mason <chris.mason@oracle.com>:
> On Tue, 2008-12-16 at 14:57 -0500, Thomas Harning wrote:
>> A kernel 'BUG' was caught while I had compression enabled and was
>> performing a 'portage' update on my gentoo installation (which had
>> btrfs mounted for portage for some basic perf testing). It has
>> finished the rsync and was at the 55% mark of the portage cache
>> update... if that helps at all.
>>
>> Inlined is the kernel bug output... + some extra debug info that had
>> been spit out beforehand that i thought might be useful...
>>
>> didn't appear to be at that 85% freespace mark...
>>
>> should I attach a btrfs-image dump?
>>
>> /dev/mapper/vg-btrfsTest
>> 1.0G 309M 716M 31% /mnt/btrfsTest
>>
>
> Looking at the logs, your disk really was full. Btrfs breaks the disk
> up into metadata and data chunks. The allocator is much more efficient
> when the chunks are fairly large (the default is 1GB), and for smaller
> devices it tries to make them smaller.
>
> There is some tuning that needs to happen on the smaller devices to
> better balance space between data and metadata. In your case, the
> metadata block groups were all full even though the data block groups
> still had some empty space.
I can reproduce this bug at the same location, simply by running
bonnie++ on a 4GB btrfs partition. I
already wrote this one week ago to this list (4 times), but it did not
show up on the list.
>
>
> -chris
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Julian Andres Klode - Free Software Developer
Debian Developer - Contributing Member of SPI
Ubuntu Member - Fellow of FSFE
Website: http://jak-linux.org/ XMPP: juliank@jabber.org
Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/
Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/
next prev parent reply other threads:[~2008-12-19 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 19:57 kernel BUG: kernel bug caught at 55% mark of portage cache update Thomas Harning
2008-12-19 16:16 ` Chris Mason
2008-12-19 16:24 ` Julian Andres Klode [this message]
2008-12-19 16:32 ` Chris Mason
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=f0d609a70812190824o24b04d90j272476e149d6cff3@mail.gmail.com \
--to=jak@jak-linux.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=thomas.harning@trustbearer.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