I can't tell what this btrfs-balance script is doing because not every btrfs balance command is in the log. It may be doing something not advisable or suboptimal or unexpected that along with some other bug is causing this to happen
Metadata,DUP: Size:107.00GiB, Used:2.11GiB I'd try to use -musage filter alone, in whatever increments work. So try 0. Then 5. If 5 fails, try 2. Increment until size is not much more than 2-3x used. Something is happening with the usage of this file system that's out of the ordinary. This is the first time I've seen such a large amount of unused metadata allocation. And then for it not only fail to balance, but for the allocation amount to increase is a first. So understanding the usage is important to figuring out what's happening. I'd file a bug and include as much information on how the fs got into this state as possible. And also if possible make a btrfs-image using the proper flags to blot out the filenames for privacy. And what btrfs-progs tools were used to create this file system. Etc. The alternative if this can't be fixed, is to recreate the filesystem because there's no practical way yet to migrate so many snapshots to a new file system. 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
