On Thu, 26 May 2016, Zhiqiang Wang wrote: > Hi all, > > In the current implementation, the base pool's snap info is well > propagated to the cache pool. However, this is not vice verse. When > creating a pool snap on the cache pool, this information is not shared > with the base. And it could potentially be overwritten by the later > snap operations on the base pool. Should we allow pool snap operations > on the cache pool? We shouldn't allow them on the cache pool. > Another question is that is it safe to clear all the snap infos on the > cache pool when removing the cache tiering? This seems ok to me if the > base and cache pools' snap infos are identical. I'm asking this > because if the snap infos are not cleared on the cache pool, it > prevents us from using this pool as a cache pool again. Yeah, we should clear them. There should also be the check that the pool is in fact empty when this happens (that should already be there...). sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
