Hi, as you might have noticed, the [1] wiki Status page lists the free-space-tree as 'Unstable', referencing a problem with the bitmap endianity. This will affect only bigendian systems.
There's one more problem that I overlooked but was pointed to by Omar recently. The initial FST support in btrfs-progs is read-only, https://marc.info/?l=linux-btrfs&m=144113538017042 "However, we're not adding the FREE_SPACE_TREE read-only compat bit to the set of supported bits because progs doesn't know how to keep the free space tree consistent." Historically, the initial patchset version did not recognize FST feature and thus refused to write, but then it was pointed by Qu and Holger that the compat_ro bit is missing for FST. I've added it but this was a mistake. This change is going to be reverted. So the status of FST is unchanged (for testing only), we still have bugs to fix. [1] https://btrfs.wiki.kernel.org/index.php/Status -- 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
