From: Josef Bacik <josef@redhat.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Mason <chris.mason@oracle.com>
Subject: Re: Entirely unexpected ENOSPC?
Date: Wed, 4 Mar 2009 13:50:53 -0500 [thread overview]
Message-ID: <20090304185053.GI5446@unused.rdu.redhat.com> (raw)
In-Reply-To: <20090304180619.GA3282@selene>
On Wed, Mar 04, 2009 at 06:06:19PM +0000, Hugo Mills wrote:
> Last night, this event jammed up a good chunk of my server:
>
> Mar 4 01:51:36 vlad kernel: btrfs searching for 1716224 bytes, num_bytes 1716224, loop 2, allowed_alloc 1
> Mar 4 01:51:36 vlad kernel: btrfs searching for 860160 bytes, num_bytes 860160, loop 2, allowed_alloc 1
> [lots of this...]
> Mar 4 01:55:52 vlad kernel: btrfs searching for 4096 bytes, num_bytes 4096, loop 2, allowed_alloc 1
> Mar 4 01:55:52 vlad kernel: btrfs allocation failed flags 1, wanted 4096
> Mar 4 01:55:52 vlad kernel: space_info has 0 free, is full
> Mar 4 01:55:52 vlad kernel: block group 12582912 has 8388608 bytes, 8388608 used 0 pinned 0 reserved
> Mar 4 01:55:52 vlad kernel: 0 blocks of free space at or bigger than bytes is
> Mar 4 01:55:52 vlad kernel: block group 1103101952 has 1073741824 bytes, 1073741824 used 0 pinned 0 reserved
> Mar 4 01:55:52 vlad kernel: 0 blocks of free space at or bigger than bytes is
> [30 more lines of this]
So yeah thats expected, you ran out of space. The key thing is this
Mar 4 01:55:52 vlad kernel: space_info has 0 free, is full
If space_info has 0 free and is full, then there is no space to allocate for it
and its completely used. I'd recommend switching to the -rc7 kernel since that
has things in place to keep this from happening as often. Thanks,
Josef
next prev parent reply other threads:[~2009-03-04 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 18:06 Entirely unexpected ENOSPC? Hugo Mills
2009-03-04 18:50 ` Josef Bacik [this message]
2009-03-04 20:48 ` Hugo Mills
-- strict thread matches above, loose matches on Subject: below --
2009-03-08 7:32 Yien Zheng
2009-03-08 7:36 ` Yien Zheng
2009-03-08 8:35 ` Dmitri Nikulin
2009-03-09 13:08 ` Yien Zheng
2009-03-09 13:20 ` Hugo Mills
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=20090304185053.GI5446@unused.rdu.redhat.com \
--to=josef@redhat.com \
--cc=chris.mason@oracle.com \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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