public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tore Anderson <tore.anderson@redpill-linpro.com>
To: Chris Mason <chris.mason@oracle.com>,
	Josef Bacik <josef@redhat.com>,
	linux-btrfs@vger.kernel.org, Hugo Mills <hugo-lkml@carfax.org.uk>
Subject: Re: Crash in __btrfs_reserve_extent
Date: Fri, 07 Aug 2009 00:01:51 +0200	[thread overview]
Message-ID: <4A7B52CF.2030105@redpill-linpro.com> (raw)
In-Reply-To: <20090806192219.GD17129@think>

Hi,

* Josef Bacik

>> Sorry about all of this, hopefully a better solution will be
>> coming down in a few months.

Don't be - the only reason why I'm running btrfs at this point is to
test and hopefully help out improving it by reporting the problems I'm
running into.  :-)

Thanks for the suggestions!

* Chris Mason

> 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.

There's no critical data on this filesystem, it's only used for my
Fedora installation.  Won't take me long to re-install from scratch if
that's what it takes.  All og my important data (home directory) is on
NFS.  Using NFS I can easily get new versions of btrfs-progs onto the
box with the hosed btrfs, too.

So if you meant to code up the fix as a band-aid only for me, don't
bother (but thanks for the offer)!  On the other hand, if you wanted to
get such a fix into btrfs-progs anyway I'll be happy to test it out for you.

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27

  reply	other threads:[~2009-08-06 22:01 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
2009-08-06 22:01                       ` Tore Anderson [this message]
  -- 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=4A7B52CF.2030105@redpill-linpro.com \
    --to=tore.anderson@redpill-linpro.com \
    --cc=chris.mason@oracle.com \
    --cc=hugo-lkml@carfax.org.uk \
    --cc=josef@redhat.com \
    --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