Le 15/05/2017 à 10:14, Hugo Mills a écrit : > [...] >> As for limit= I'm not sure if it would be helpful since I run this >> nightly. Anything that doesn't get done tonight due to limit, would be >> done tomorrow? > I'm suggesting limit= on its own. It's a fixed amount of work > compared to usage=, which may not do anything at all. For example, > it's perfectly possible to have a filesystem which is, say, 30% full, > and yet is still fully-allocated filesystem with more than 20% of > every chunk used. In that case your usage= wouldn't balance anything, > and you'd still be left in the situation of risking ENOSPC from > running out of metadata.
Hugo, as I don't have any feedback on my approach to address this problem could you have a look at my script or simply the principle : is there any drawback vs using limit in calling balance multiple times raising usage (and using the same value for data and metadata) until you get enough free space ? For reference : https://github.com/jtek/ceph-utils/blob/master/btrfs-auto-rebalance.rb Lionel -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
