All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Shepelev <anton.txt@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Interpreting `btrfs filesystem show'
Date: Mon, 15 Oct 2018 17:24:08 +0300	[thread overview]
Message-ID: <20181015172408.1b3867debea3951fb7014ee4@gmail.com> (raw)

Hello, all

While trying to resolve free space problems, and found that
I cannot interpret the output of:

> btrfs filesystem show

Label: none  uuid: 8971ce5b-71d9-4e46-ab25-ca37485784c8
        Total devices 1 FS bytes used 34.06GiB
        devid    1 size 40.00GiB used 37.82GiB path /dev/sda2

How come the total used value is less than the value listed
for the only device?

-- 
()  ascii ribbon campaign - against html e-mail
/\  http://preview.tinyurl.com/qcy6mjc [archived]

             reply	other threads:[~2018-10-15 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 14:24 Anton Shepelev [this message]
2018-10-15 14:26 ` Interpreting `btrfs filesystem show' Hugo Mills
2018-10-15 14:30   ` Hugo Mills
     [not found]   ` <20181015174040.6f4962336386d8549026908c@gmail.com>
2018-10-15 14:42     ` Anton Shepelev
2018-10-15 15:02       ` Austin S. Hemmelgarn
2018-10-15 15:48   ` Martin Steigerwald

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=20181015172408.1b3867debea3951fb7014ee4@gmail.com \
    --to=anton.txt@gmail.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.