From: Chris Mason <chris.mason@oracle.com>
To: Tom van Klinken / ISP Services BV <tom@isp-services.nl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Crash in 2.6.29-rc8
Date: Wed, 01 Apr 2009 13:58:31 -0400 [thread overview]
Message-ID: <1238608711.18549.58.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49D1FDFC.3090904@isp-services.nl>
On Tue, 2009-03-31 at 13:26 +0200, Tom van Klinken / ISP Services BV
wrote:
> Hi Chris,
>
> Chris Mason wrote:
> > On Tue, 2009-03-24 at 15:41 +0100, Tom van Klinken / ISP Services BV
> > wrote:
> >> <CUT>
> >
> > This is a metadata enospc oops. You actually had about 400MB free but
> > it was pinned down and waiting for a commit to free it all.
> >
> Today I had a similar issue. See attached kernel trace.
>
> I'm quite sure the filesystem is not full (I have around 15GB of free
> space).
>
> Is their anything I can test/do?
>
> plain text document attachment (btrfc-trace2.txt)
> Mar 31 00:20:07 db03b btrfs searching for 4096 bytes, num_bytes 4096, loop 2, allowed_alloc 0
> Mar 31 00:20:07 db03b btrfs allocation failed flags 36, wanted 4096
> Mar 31 00:20:07 db03b space_info has 204537856 free, is full
Well, the problem is that you've filled up the metadata areas of your
FS. So, even though the FS reads 15GB free, the space available for
metadata is full.
I'm working on some patches to help.
-chris
prev parent reply other threads:[~2009-04-01 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 14:41 Crash in 2.6.29-rc8 Tom van Klinken / ISP Services BV
2009-03-24 17:43 ` Chris Mason
2009-03-31 11:26 ` Tom van Klinken / ISP Services BV
2009-04-01 17:58 ` 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=1238608711.18549.58.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tom@isp-services.nl \
/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