Hi Stefan, On Sat, Apr 26, 2014 at 11:28 PM, Chris Murphy <li...@colorremedies.com> wrote: >>> >>> They're harmless -- it's a side-effect of the way that mkfs works. >>> They'll go away if you balance them: >>> >>> btrfs balance start -dprofiles=single -mprofiles=single -sprofiles=single >>> /mountpoint >> >> btrfs refused this command, I had to pass --force to execute it. >> It exited with this:Done, had to relocate 2 out of 2710 chunks. >> >> After that btrfs fi df shows the following: >> >> Data, RAID1: total=2.64TiB, used=2.22TiB >> System, RAID1: total=8.00MiB, used=380.00KiB >>> System, single: total=4.00MiB, used=0.00< >> Metadata, RAID1: total=4.00GiB, used=2.94GiB > > Hmm, seems like a bug. What about
See this patch: "Btrfs: stop refusing the relocation of chunk 0" I managed to balance away the empty single System chunk only once I was running 3.13 from Ubuntu trusty. http://www.spinics.net/lists/linux-btrfs/msg27119.html https://bugzilla.kernel.org/show_bug.cgi?id=60594 Cheers, Dan -- 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
