linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: "Kline, Matthew" <matthew.kline@flukenetworks.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs balance fails with no space errors (despite having plenty)
Date: Wed, 25 Mar 2015 04:31:13 +0500	[thread overview]
Message-ID: <20150325043113.35bd9078@natsu> (raw)
In-Reply-To: <E8C63C11EA3FB04DBDFEDECEFD927FD1140C1E65@US-EVT-EXM04-P.global.tektronix.net>

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

On Tue, 24 Mar 2015 23:09:47 +0000
"Kline, Matthew" <matthew.kline@flukenetworks.com> wrote:

> Data, single: total=44.00GiB, used=43.37GiB
> System, single: total=32.00MiB, used=12.00KiB
> Metadata, single: total=2.00GiB, used=876.84MiB
> GlobalReserve, single: total=296.00MiB, used=0.00B
> 
> Total partition size is 322 GB, as given by `parted -l` (I misspoke in the last email - the drive is only 14% full)

Okay that's some different issue then, doesn't look like what I had, where on
a 9 TB FS after conversion I got 2 TB of metadata (with 1.2TB free space).

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2015-03-24 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 22:25 btrfs balance fails with no space errors (despite having plenty) Kline, Matthew
2015-03-24 23:03 ` Roman Mamedov
2015-03-24 23:09   ` Kline, Matthew
2015-03-24 23:14     ` Hugo Mills
2015-03-24 23:45       ` Kline, Matthew
2015-03-25  3:39       ` Russell Coker
2015-03-24 23:31     ` Roman Mamedov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-12 18:48 Kline, Matthew
2014-11-13  0:06 ` Oon-Ee Ng
2014-11-13  7:36 ` Duncan
2014-11-13 10:38 ` Hugo Mills

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=20150325043113.35bd9078@natsu \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=matthew.kline@flukenetworks.com \
    /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).