From: Chris Mason <chris.mason@oracle.com>
To: Josef Bacik <josef@redhat.com>
Cc: Tore Anderson <tore.anderson@redpill-linpro.com>,
linux-btrfs@vger.kernel.org, Hugo Mills <hugo-lkml@carfax.org.uk>
Subject: Re: Crash in __btrfs_reserve_extent
Date: Thu, 6 Aug 2009 15:22:19 -0400 [thread overview]
Message-ID: <20090806192219.GD17129@think> (raw)
In-Reply-To: <20090806190118.GI3655@dhcp231-156.rdu.redhat.com>
On Thu, Aug 06, 2009 at 03:01:18PM -0400, Josef Bacik wrote:
> On Thu, Aug 06, 2009 at 08:49:39PM +0200, Tore Anderson wrote:
> > * Josef Bacik
> >
> > > Ok good news is, btrfs-vol -b will fix your problem. Somehow most of
> > > your disk has been allocated to use metadata. So did you have a
> > > whole bunch of stuff on this disk and then delete it all? Because
> > > that would put you in that situation. If you have not then there is
> > > likely a bug in the metadata ratio stuff that needs to be fixed.
> >
> > As far as I know there hasn't been a lot of stuff on the file system,
> > I'm afraid. The file system was created by the Fedora 11 installer,
> > and it has just been used as the system drive (I've got /home on NFS).
> >
> > btrfs-vol -b / (from btrfs-progs-0.19) made my system crash and burn.
> > I've was able to get output from dmesg before my SSH sessions started
> > hanging - maybe you can make anything out of it? Anyway, right now I
> > have no more remote access to the box so any further debugging will
> > have to wait until tomorrow morning.
> >
>
> Hrm yeah I was afraid of that. So you will have to try and free up some data so
> the balancer as enough room to move things around. Also one thing that _may_
> help is mounting with nocow for a little bit, so any writing (like logging and
> such) just over-writes stuff instead of needing a new extent, until btrfs-vol -b
> can finish, and then you can go back to the normal mount options. I still can't
> figure out how this happened, but one thing to do for now would be to mount with
> metadata_ratio=100. This will make you more likely to panic in the event that
> you run out of metadata, but its not that likely to happen, especially with as
> much disk space as you have. Sorry about all of this, hopefully a better
> solution will be coming down in a few months. Thanks,
We can code a fix for the balancer problem quickly, but you might have a
hard time recompiling it and getting it on that box.
If this data is critical we'll write something up.
-chris
next prev parent reply other threads:[~2009-08-06 19:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 7:00 Crash in __btrfs_reserve_extent Tore Anderson
2009-08-06 8:53 ` Tore Anderson
2009-08-06 13:54 ` Josef Bacik
2009-08-06 14:15 ` Tore Anderson
2009-08-06 14:27 ` Josef Bacik
2009-08-06 17:41 ` Tore Anderson
2009-08-06 18:04 ` Josef Bacik
2009-08-06 18:14 ` Tore Anderson
2009-08-06 18:37 ` Josef Bacik
2009-08-06 18:49 ` Tore Anderson
2009-08-06 18:57 ` Chris Mason
2009-08-06 19:01 ` Josef Bacik
2009-08-06 19:22 ` Chris Mason [this message]
2009-08-06 22:01 ` Tore Anderson
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 14:57 Robert Förster
2009-08-06 15:20 ` Josef Bacik
2009-08-06 15:36 ` Robert Förster
2009-08-07 5:10 ` Robert Förster
2009-08-06 17:15 ` Tore Anderson
2009-08-06 17:57 ` Robert Förster
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=20090806192219.GD17129@think \
--to=chris.mason@oracle.com \
--cc=hugo-lkml@carfax.org.uk \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tore.anderson@redpill-linpro.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