linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: how to run balance successfully (No space left on device)?
Date: Mon, 18 Sep 2017 17:20:22 +0900	[thread overview]
Message-ID: <19a1770cf67e63a84c3baeeb44af9e9a@wpkg.org> (raw)
In-Reply-To: <5ff267d206ae631e9d259eacacdf7924@wpkg.org>

>> # df -h /var/lib/lxd
>> 
>> FWIW, standard (aka util-linux) df is effectively useless in a 
>> situation
>> such as this, as it really doesn't give you the information you need 
>> (it
>> can say you have lots of space available, but if btrfs has all of it
>> allocated into chunks, even if the chunks have space in them still, 
>> there
>> can be problems).

I see here on RAID-1, "df -h" it shows pretty much the same amount of 
free space as "btrfs fi show":

- "df -h" shows 105G free
- "btrfs fi show" says: Free (estimated):            104.28GiB      
(min: 104.28GiB)



> But chances are pretty good that one you get that patch integrated,
> whether by integrating it yourself to what you have currently, or by
> trying 4.14-rc1 or waiting until it hits release or stable, that bug 
> will
> have been squashed! =:^)

OK, will wait for 4.14.


Tomasz Chmielewski
https://lxadm.com

  parent reply	other threads:[~2017-09-18  8:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17 15:02 how to run balance successfully (No space left on device)? Tomasz Chmielewski
2017-09-18  1:50 ` Duncan
2017-09-18  8:20 ` Tomasz Chmielewski [this message]
2017-09-18  8:29   ` Andrei Borzenkov
2017-09-18  9:27     ` Tomasz Chmielewski
2017-09-18 13:44       ` Peter Becker
2017-09-18 13:50         ` Tomasz Chmielewski
2017-09-19  2:59       ` Duncan
2017-10-31 14:18   ` Tomasz Chmielewski
2017-10-31 14:51     ` Tomasz Chmielewski
2017-11-07  5:13     ` Tomasz Chmielewski
     [not found]       ` <CAJtFHUQ34uyt-iAQKuQ-WqXMrCqxsPeqFc5LvYmZHrz+Rxs66A@mail.gmail.com>
2017-11-10  7:42         ` Tomasz Chmielewski
2017-11-10 21:51           ` Chris Murphy
2017-11-10 22:18             ` Martin Raiber

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=19a1770cf67e63a84c3baeeb44af9e9a@wpkg.org \
    --to=mangoo@wpkg.org \
    --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;
as well as URLs for NNTP newsgroup(s).