All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tore Anderson <tore.anderson@redpill-linpro.com>
To: Josef Bacik <josef@redhat.com>
Cc: "Robert Förster" <Dessa@gmake.de>, linux-btrfs@vger.kernel.org
Subject: Re: Crash in __btrfs_reserve_extent
Date: Thu, 06 Aug 2009 19:15:35 +0200	[thread overview]
Message-ID: <4A7B0FB7.2010401@redpill-linpro.com> (raw)
In-Reply-To: <20090806152058.GF3655@dhcp231-156.rdu.redhat.com>

* Josef Bacik

> Alrighty, so btrfs-show says you have used up all of your disk, but
> for some reason statfs is saying you havent.  Can you cd into / and
> run
> 
> du -h -s
> 
> and then wait a very long time and then tell me what it comes back
> with :). That will tell us for sure what the hell is going on.  Thank
> you,

I think this needs to be "du -h -s -x" (otherwise you'll include space
used by files on other file systems as well).

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

  parent reply	other threads:[~2009-08-06 17:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 14:57 Crash in __btrfs_reserve_extent 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 [this message]
2009-08-06 17:57     ` Robert Förster
  -- strict thread matches above, loose matches on Subject: below --
2009-08-06  7:00 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

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=4A7B0FB7.2010401@redpill-linpro.com \
    --to=tore.anderson@redpill-linpro.com \
    --cc=Dessa@gmake.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.