From: Chris Mason <chris.mason@oracle.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/inode.c:806
Date: Thu, 02 Dec 2010 11:19:56 -0500 [thread overview]
Message-ID: <1291306746-sup-1916@think> (raw)
In-Reply-To: <201012011411.02352.johannes.hirte@fem.tu-ilmenau.de>
Excerpts from Johannes Hirte's message of 2010-12-01 08:11:01 -0500:
> On one of my machines with btrfs I got this bug:
>
> entry offset 29085974528, bytes 4096, bitmap no
> entry offset 29162995712, bytes 20480, bitmap yes
> entry offset 29171744768, bytes 4096, bitmap no
> block group has cluster?: no
> 0 blocks of free space at or bigger than bytes is
> block group 29834084352 has 1073741824 bytes, 1072648192 used 0 pinned 0 reserved
Well, you've had an ENOSPC explosion.
>
> The "block group" messages where way more, too much for the dmesg log buffer.
> Kernel is a 2.6.37-rc3+ without the latest btrfs-fixes. The bug occurred when
> compiling openoffice.org. After the bug a 'df -h' showed:
>
> df -h:
> Filesystem Size Used Avail Use% Mounted on
> rootfs 21G 17G 770M 96% /
> /dev/root 21G 17G 770M 96% /
> rc-svcdir 1.0M 108K 916K 11% /lib/rc/init.d
> udev 10M 116K 9.9M 2% /dev
> shm 1013M 0 1013M 0% /dev/shm
> /dev/sda2 66G 46G 20G 71% /home
> /dev/sdb1 75G 56G 19G 75% /mnt/windows
Which of these filesystems were you compiling on?
-chris
next prev parent reply other threads:[~2010-12-02 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 13:11 kernel BUG at fs/btrfs/inode.c:806 Johannes Hirte
2010-12-02 16:19 ` Chris Mason [this message]
2010-12-02 16:52 ` Johannes Hirte
2010-12-02 17:02 ` Johannes Hirte
2010-12-02 19:21 ` Chris Mason
2010-12-03 2:01 ` Johannes Hirte
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=1291306746-sup-1916@think \
--to=chris.mason@oracle.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--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;
as well as URLs for NNTP newsgroup(s).