On Apr 26, 2014, at 12:18 PM, Stefan Malte Schumacher <s.schumac...@netcologne.de> 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 btrfs balance start -sconvert=raid1,soft -f -v > > >> btrfs fi label should do this. > > I was mainly asking because of this: > https://btrfs.wiki.kernel.org/index.php/UseCases: You can also use > btrfs command.There are currently few limitations: the filesystem has > to be unmounted the filesystem should not have more than one device > > Is this information outdated? btfs fi label is done when the system is mounted; for the change to visibly take effect in /dev/ it has to be umounted then mounted. I don't even think it takes effect with a remount, but I could be mistaken. This seems to be a btrfs limitation, if I relabel ext4 volumes while mounted, their label is changed immediately, so the behavior may change down the road. 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
