What kernel version are you using? I suggest reading the whole thread but in particular this note about CentOS 7 and Btrfs. http://www.spinics.net/lists/linux-btrfs/msg40850.html
So kernel 3.16 isn't necessarily too old, but I know there's been a lot of on-going balance related work that's not in that kernel and thus won't be in the CentOS 7.1 kernel either. And then there's also some possibility the older btrfs-progs contributes to the problem, even though I think most of the balance code is actually in the kernel. While the CentOS 7.1 kernel is going to be more stable/predictable overall (not with respect to Btrfs but everything the kernel does): a.) Btrfs is a tech preview b.) To unwind the problems you've having with this volume right now, I'd really suggest a much newer kernel. > Total devices 2 FS bytes used 17.06GiB > devid 1 size 111.11GiB used 22.03GiB path /dev/sdf3 > devid 2 size 111.11GiB used 22.03GiB path /dev/sdg3 There's tons of unallocated space for new data or metadata chunks. > Data, RAID1: total=18.00GiB, used=16.36GiB > System, RAID1: total=32.00MiB, used=16.00KiB > Metadata, RAID1: total=4.00GiB, used=711.34MiB > GlobalReserve, single: total=240.00MiB, used=128.00KiB > ERROR: error during balancing '/' - No space left on device And there's tons of space in already created data and metadata chunks. So something is wrong, and I really wouldn't persist on trying to make this work with an older kernel and progs. So I suggest putting the volume on a system with a 4.1 kernel and 4.1 progs, and running a btrfs check without --repair and report back with the full output. Once you get things fixed up, it seems going back to the CentOS 7.1 kernel is fine. But periodically you might have to revert to a newer kernel for some maintenance, at least until the fix for the problem makes it into a future CentOS kernel. 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
