On Sep 15, 2014, at 11:37 AM, Mark Murawski <markm-li...@intellasoft.net> wrote:
> btrfs balance start -dusage=86 /
> Done, had to relocate 1 out of 13 chunks
>
> cartman {~} root# btrfs fi df /
> Data, RAID1: total=7.03GiB, used=7.01GiB
> System, RAID1: total=32.00MiB, used=4.00KiB
> Metadata, RAID1: total=1.00GiB, used=438.88MiB
> unknown, single: total=148.00MiB, used=0.00
>
> What's this 'unknown' section? Maybe this is the problem? How do I get rid
> of it?
It's not a problem, it's cosmetic for now, something introduced in kernel 3.15
but progs doesn't yet give a label for.
>
> I still get enospc after a balance with a filter, and then a regular balance:
>
> cartman {~} root# btrfs balance start /
> ERROR: error during balancing '/' - No space left on device
Maybe try mount option enospc_debug and retry, see if you get more information
in dmesg.
I'm not sure if a balance in this case wants to create a new data and metadata
chunk (on each device), or if it can start without creating any chunks. If it
wants to create new chunks, it's 1GiB for data, and 256MiB for metadata. That's
1.256GiB but you only have 1.25GiB unallocated on each device: size 9.31GiB
minus used 8.06GiB.
Chris Murphy--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
