Bug #55
closed
osd: fix transition from snaps -> no snaps -> snaps
Added by Sage Weil about 14 years ago.
Updated over 13 years ago.
Description
After filestore btrfs snaps = 1 -> 0, we may have leftover snap dirs. Later, if we turn them back on again, we'll roll back to a horribly ancient state.
- Target version changed from v0.21 to v0.22
- Target version changed from v0.22 to v0.23
I think all we need to do is look at current/commit_op_seq. If it is greater than the newest snap, than that snap is stale, because someone went and committed to current/.
An optional arg --osd-use-stale-snap bool would override that. That way you could still manually roll back to an older snap (by, say, deleting/renaming the newest) if you needed to for some reason.
- Assignee set to Yehuda Sadeh
- Status changed from New to Resolved
- Translation missing: en.field_position deleted (
317)
- Translation missing: en.field_position set to 183
Also available in: Atom
PDF