On Sun, Nov 19, 2017 at 7:24 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > $ sudo fstrim -v / > /: 39 GiB (41841328128 bytes) trimmed > And trim again: > > /: 39 GiB (41841328128 bytes) trimmed Cute. The balance command claimed it balanced a chunk but it didn't. btrfs-debug -b says that same 8% chunk is present... block group offset 175275769856 len 1073741824 used 89206784 chunk_objectid 256 flags 1 usage 0.08 Fine. I'll do a -duage instead. $ sudo btrfs balance start -dusage=11 / Done, had to relocate 2 out of 32 chunks $ sudo fstrim -v / /: 40 GiB (42915069952 bytes) trimmed $ sudo btrfs balance start -dusage=21 / Done, had to relocate 2 out of 31 chunks $ sudo fstrim -v / /: 41 GiB (43988811776 bytes) trimmed OK so a different bug is that it's claiming to balance two chunks but it's really only balancing one. That same 8% used block group was not rewritten, it's at the same address, so for whatever reason that tiny one is pinned. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
