From: Chris Mason <chris.mason@oracle.com>
To: Thomas Harning <thomas.harning@trustbearer.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG: kernel bug caught at 55% mark of portage cache update
Date: Fri, 19 Dec 2008 11:16:19 -0500 [thread overview]
Message-ID: <1229703379.6695.18.camel@think.oraclecorp.com> (raw)
In-Reply-To: <FD060D90-0C58-4222-8A56-CDE0B47AD6DC@trustbearer.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.
-chris
next prev parent reply other threads:[~2008-12-19 16:16 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 [this message]
2008-12-19 16:24 ` Julian Andres Klode
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=1229703379.6695.18.camel@think.oraclecorp.com \
--to=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