On 09/01/2015 03:05 PM, Omar Sandoval wrote:
From: Omar Sandoval <osandov@xxxxxx> Now we can finally hook up everything so we can actually use free space tree. On the first mount with the free_space_tree mount option, the free space tree will be created and the FREE_SPACE_TREE read-only compat bit will be set. Any time the filesystem is mounted from then on, we will use the free space tree. Having both the free space cache and free space trees enabled is nonsense, so we don't allow that to happen. Since mkfs sets the superblock cache generation to -1, this means that the filesystem will have to be mounted with nospace_cache,free_space_tree to create the free space trees on first mount. Once the FREE_SPACE_TREE bit is set, the cache generation is ignored when mounting. This is all a little more complicated than would be ideal, but at some point we can presumably make the free space tree the default and stop setting the cache generation in mkfs. Signed-off-by: Omar Sandoval <osandov@xxxxxx>
Reviewed-by: Josef Bacik <jbacik@xxxxxx> Thanks, Josef -- 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
