From: Chris Mason <chris.mason@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: add a "df" ioctl for btrfs
Date: Wed, 13 Jan 2010 09:29:23 -0500 [thread overview]
Message-ID: <20100113142923.GL14979@think> (raw)
In-Reply-To: <20100113102503.GA6887@infradead.org>
On Wed, Jan 13, 2010 at 05:25:03AM -0500, Christoph Hellwig wrote:
> On Tue, Jan 12, 2010 at 03:25:13PM -0500, Josef Bacik wrote:
> > df is a very loaded question in btrfs. This gives us a way to get the per-space
> > usage information so we can tell exactly what is in use where. This will help
> > us figure out ENOSPC problems, and help users better understand where their disk
> > space is going.
>
> Just as discussed before I think it's a really bad idea. We always had
> df reporting inconsistencies due to the way metadata is managed, and
> btrfs isn't special in that way.
This is more than just df being inaccurate, it's a way to find out how
much space is used by each of the raid modes. We've had a ton of
feature requests for this, and it really helps identify drives that have
a ton of free space tied up for data vs metadata.
-chris
next prev parent reply other threads:[~2010-01-13 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 20:25 [PATCH] Btrfs: add a "df" ioctl for btrfs Josef Bacik
2010-01-12 20:34 ` Josef Bacik
2010-01-13 10:25 ` Christoph Hellwig
2010-01-13 13:33 ` Josef Bacik
2010-01-13 14:29 ` Chris Mason [this message]
2010-01-13 21:46 ` Christoph Hellwig
2010-01-14 0:55 ` Chris Mason
2010-01-13 14:31 ` Chris Mason
2010-01-13 18:19 ` Josef Bacik
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=20100113142923.GL14979@think \
--to=chris.mason@oracle.com \
--cc=hch@infradead.org \
--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.