On Thu, 5 Apr 2012, Henry C Chang wrote: > Hi folks, > > I created a pool without adding any osds to it in the crushmap. As > expected, all pgs remains in creating state since no osds take care of > them. > > However, I do expect that this pool should be able to be removed. > Currently, removing such a pool hangs forever as the pg removal has to > wait until the pg have been created. Does my expectation make sense? Yeah. I seem to remember the pg removal code cleaning up stuff in the monitor's PGMap, but I'm also pretty sure this scenario was never tested. Do you see where it is waiting for PG creation? I don't think it should need to do that, since it's going to be thrown out anyway. 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
