linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Chris Murphy <lists@colorremedies.com>
Cc: Tim Eggleston <lists@timeggleston.co.uk>, linux-btrfs@vger.kernel.org
Subject: Re: RAID10 total capacity incorrect
Date: Sun, 2 Jun 2013 18:43:59 +0100	[thread overview]
Message-ID: <20130602174359.GI20133@carfax.org.uk> (raw)
In-Reply-To: <099CD4A1-A70D-4446-8C55-843D21BE4E7F@colorremedies.com>

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

On Sun, Jun 02, 2013 at 12:52:40PM -0400, Chris Murphy wrote:
> 
> On Jun 2, 2013, at 12:17 PM, Tim Eggleston <lists@timeggleston.co.uk> wrote:
> > 
> > root@mckinley:/# btrfs fi df /mnt/shares/btrfsvol0
> > Data, RAID10: total=2.06TB, used=2.06TB
> > System, RAID10: total=64.00MB, used=188.00KB
> > System: total=4.00MB, used=0.00
> > Metadata, RAID10: total=3.00GB, used=2.29GB
> > 
> > 
> > Am I being an idiot and missing something here? 

> No, it's confusing. btrfs fi df doesn't show free space. The first
> value is what space the fs has allocated for the data usage type,
> and the 2nd value is how much of that allocation is actually being
> used. I personally think the allocated value is useless for mortal
> users. I'd rather have some idea of what free space I have left, and
> the regular df command presents this in an annoying way also because
> it shows the total volume size, not accounting for the double
> consumption of raid1. So no matter how you slice it, it's confusing.

   It's the nature of the beast, unfortunately. So far, nobody's
managed to come up with a simple method of showing free space and
space usage that isn't going to be misleading somehow.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
         --- If you're not part of the solution, you're part ---         
                           of the precipiate.                            

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-06-02 17:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 16:17 RAID10 total capacity incorrect Tim Eggleston
2013-06-02 16:30 ` Hugo Mills
2013-06-02 16:52   ` Tim Eggleston
2013-06-02 17:41     ` Hugo Mills
2013-06-02 16:52 ` Chris Murphy
2013-06-02 17:43   ` Hugo Mills [this message]
2013-06-03  5:26     ` Duncan
2013-06-03  8:02       ` Tim Eggleston
2013-06-04  5:30         ` Duncan

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=20130602174359.GI20133@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=lists@timeggleston.co.uk \
    /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;
as well as URLs for NNTP newsgroup(s).