public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ahmed Kamal <email.ahmedkamal@googlemail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel .32, btrfs-vol -b, why is metadata=data
Date: Mon, 7 Dec 2009 22:26:43 +0200	[thread overview]
Message-ID: <3da3b5b40912071226t793bf96avad30b2b62737b0a0@mail.gmail.com> (raw)
In-Reply-To: <20091207153849.GA2859@think>

> In other words, btrfs-show could tell you that 19GB has been used, but
> df could say that 0 bytes are in use in the FS.

Thanks Chris for the clarification. So despite saying 19G are used, I
shouldn't be worried about running out of disk space, since these are
just pre-allocated areas. Perhaps btrfs-show should show how much
areas are really used, besides how much are just pre-allocated. The
thing is, I keep monitoring that number to avoid ENOSPC and now I know
that number is not accurate.

Thanks for the stellar work
Regards

      reply	other threads:[~2009-12-07 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06  8:50 kernel .32, btrfs-vol -b, why is metadata=data Ahmed Kamal
2009-12-07 15:38 ` Chris Mason
2009-12-07 20:26   ` Ahmed Kamal [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=3da3b5b40912071226t793bf96avad30b2b62737b0a0@mail.gmail.com \
    --to=email.ahmedkamal@googlemail.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