linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Donald Pearson <donaldwhpearson@gmail.com>
To: Rich Rauenzahn <rrauenza@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs full, but not full, can't rebalance
Date: Fri, 3 Jul 2015 01:05:39 -0500	[thread overview]
Message-ID: <CAC=t97DWVCNVPF7tiEou3okRB-LED37WOcp3TmVZMEcgagZD7g@mail.gmail.com> (raw)
In-Reply-To: <CAG+QAKURSWktf6orSV5Aeh0LTrHCjap5pL9XyyERO1+9bZxZaQ@mail.gmail.com>

what does the fi df , or btrfs fi usage show now

On Fri, Jul 3, 2015 at 1:03 AM, Rich Rauenzahn <rrauenza@gmail.com> wrote:
> Yes -- I just figured that out as well!
>
> Now why did it suddenly fill up?   (I still get the failure rebalancing ...)
>
> # btrfs fi show /
> Label: 'centos7'  uuid: 35f0ce3f-0902-47a3-8ad8-86179d1f3e3a
>         Total devices 4 FS bytes used 17.12GiB
>         devid    1 size 111.11GiB used 111.05GiB path /dev/sdf3
>         devid    2 size 111.11GiB used 111.05GiB path /dev/sdg3
>         devid    3 size 5.00GiB used 5.00GiB path /dev/loop1
>         devid    4 size 5.00GiB used 5.00GiB path /dev/loop2
>
> Btrfs v3.16.2
>
>
> On Thu, Jul 2, 2015 at 11:01 PM, Donald Pearson
> <donaldwhpearson@gmail.com> wrote:
>> Because this is raid1 I believe you need another for that to work.
>>
>> On Fri, Jul 3, 2015 at 12:57 AM, Rich Rauenzahn <rrauenza@gmail.com> wrote:
>>> Yes, I tried that -- and adding the loopback device.
>>>
>>> # btrfs device add /dev/loop1 /
>>> Performing full device TRIM (5.00GiB) ...
>>>
>>> # btrfs fi show /
>>> Label: 'centos7'  uuid: 35f0ce3f-0902-47a3-8ad8-86179d1f3e3a
>>>         Total devices 3 FS bytes used 17.13GiB
>>>         devid    1 size 111.11GiB used 111.10GiB path /dev/sdf3
>>>         devid    2 size 111.11GiB used 111.10GiB path /dev/sdg3
>>>         devid    3 size 5.00GiB used 0.00 path /dev/loop1
>>>
>>> Btrfs v3.16.2
>>>
>>> # btrfs balance start -m /
>>> ERROR: error during balancing '/' - No space left on device
>>> There may be more info in syslog - try dmesg | tail
>>>
>>> # btrfs balance start -v -dusage=1 /
>>> Dumping filters: flags 0x1, state 0x0, force is off
>>>   DATA (flags 0x2): balancing, usage=1
>>> ERROR: error during balancing '/' - No space left on device
>>> There may be more info in syslog - try dmesg | tail
>>>
>>>
>>>
>>> On Thu, Jul 2, 2015 at 10:45 PM, Donald Pearson
>>> <donaldwhpearson@gmail.com> wrote:
>>>> Have you seen this article?
>>>>
>>>> I think the interesting part for you is the "balance cannot run
>>>> because the filesystem is full" heading.
>>>>
>>>> http://marc.merlins.org/perso/btrfs/post_2014-05-04_Fixing-Btrfs-Filesystem-Full-Problems.html
>>>>
>>>> On Fri, Jul 3, 2015 at 12:32 AM, Rich Rauenzahn <rrauenza@gmail.com> wrote:
>>>>> Running on CentOS7 ... / got full, I removed the files, but it still
>>>>> thinks it is full.  I've tried following the FAQ, even adding a
>>>>> loopback device during the rebalance.
>>>>>
>>>>> # btrfs fi show /
>>>>> Label: 'centos7'  uuid: 35f0ce3f-0902-47a3-8ad8-86179d1f3e3a
>>>>>         Total devices 2 FS bytes used 24.27GiB
>>>>>         devid    1 size 111.11GiB used 111.05GiB path /dev/sdf3
>>>>>         devid    2 size 111.11GiB used 111.05GiB path /dev/sdg3
>>>>>
>>>>> # btrfs fi df /
>>>>> Data, RAID1: total=107.02GiB, used=22.12GiB
>>>>> System, RAID1: total=32.00MiB, used=16.00KiB
>>>>> Metadata, RAID1: total=4.05GiB, used=2.15GiB
>>>>> GlobalReserve, single: total=512.00MiB, used=0.00
>>>>>
>>>>> # btrfs balance start -v -dusage=1 /
>>>>> Dumping filters: flags 0x1, state 0x0, force is off
>>>>>   DATA (flags 0x2): balancing, usage=1
>>>>> ERROR: error during balancing '/' - No space left on device
>>>>> There may be more info in syslog - try dmesg | tail
>>>>>
>>>>> # btrfs balance start -m /
>>>>> ERROR: error during balancing '/' - No space left on device
>>>>> There may be more info in syslog - try dmesg | tail
>>>>>
>>>>> What can I do?
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-07-03  6:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  5:32 btrfs full, but not full, can't rebalance Rich Rauenzahn
2015-07-03  5:45 ` Donald Pearson
2015-07-03  5:57   ` Rich Rauenzahn
2015-07-03  6:01     ` Donald Pearson
2015-07-03  6:03       ` Rich Rauenzahn
2015-07-03  6:05         ` Donald Pearson [this message]
2015-07-03  7:56     ` Rich Rauenzahn
2015-07-03 17:28       ` Rich Rauenzahn
2015-07-03 18:04         ` Chris Murphy
2015-07-12  6:10           ` Rich Rauenzahn

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='CAC=t97DWVCNVPF7tiEou3okRB-LED37WOcp3TmVZMEcgagZD7g@mail.gmail.com' \
    --to=donaldwhpearson@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rrauenza@gmail.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).