On Wed, Feb 11, 2015 at 4:09 AM, GuangYang <yguang11@xxxxxxxxxxx> wrote: > Hi ceph-devel, > Recently we are trying the upgrade from Firefly to Giant and it goes pretty smoothly, however, the problem is that it does not support rollback and seems like that is by design. For example, there is new feature flag / metadata [1] added in the new version and they are persisted. As a result, the old version of software does not recognize those values and will crash themselves. > > Ideally we never rollback, but for unknown reasons we couldn't fix in a timely manner, we might want to rollback first. Is that something we will consider to handle? We are unlikely to ever do this. We've talked about rollback options, but allowing rollback means either: 1) never adding information to the disk format which matters, 2) having a separate switchover point (besides the code upgrade) which enables all the disk change bits and which doesn't allow you to roll back. The first option is obviously infeasible. The second one dramatically increases the amount of code which can be buggy, increases the testing version, and doesn't really solve the problem since you still have a hard point of no return. -Greg -- 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
