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: Tue, 24 Mar 2009 13:43:06 -0400 [thread overview]
Message-ID: <1237916586.5633.14.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49C8F103.1090407@isp-services.nl>
On Tue, 2009-03-24 at 15:41 +0100, Tom van Klinken / ISP Services BV
wrote:
> Hi,
>
> I started using btrfs yesterday and used the version that comes with
> 2.6.29-rc8.
>
> The main reason I wanted to try btrfs is that because I am running on
> SSD's and the normal wear leveling algorithm of this SSD (MTRON 7535)
> failed terribly with xfs. (SSD's wore out in 2 months)
>
> I have a 64GB ssd mounted with '-o noatime' and '-o ssd'.
>
> The load is MySQL with 300-400 inserts/sec 24/7 on a large database with
> a lot of indexes.
>
> Attached is the trace I got this morning. The system ran fine for about
> 16 hours :)
>
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.
There is definitely more work to do on the metadata enospc side of
things. One possible problem is that your disk is full of data block
groups and more metadata groups are required.
I'll work on some more metadata enospc patches this week.
-chris
next prev parent reply other threads:[~2009-03-24 17:43 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 [this message]
2009-03-31 11:26 ` Tom van Klinken / ISP Services BV
2009-04-01 17:58 ` 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=1237916586.5633.14.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