-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prune bookmarks ? #771
Comments
Could we imagine this strategy, when using --no-sync-snap, maybe a new option --create-per-destination-bookmark : After a successful send, create on the source one bookmark which name derives from the destination. It will simply point to the latest sent snapshot to that destination. If the bookmark already exists, destroy it before creating it again (we're moving the bookmark). The option --create-bookmark creates a bookmark with same name as the snapshot, but I find this not very useful, because it will accumulate and also because we don't know which ones can be deleted when there are several destinations. |
i have created a prune script which seems to work good for me. you can pass the number of days to keep as a param. value it must be greater then some $numdayssafe which is set inside the script, so nobody would delete too many bookmarks accidentally
|
|
i'm getting a little bit nervous....but i dislike the extra prune-script approach. could we please have a bookmark prune feature ?
|
There is no real need other than to make you feel warm and fuzzy. Bookmarks take up almost 0 space. |
did you ever try to delete 40k zfs booksmarks @beren12 ? a bookmark is an object, and every object takes ressources and runtime.
|
Do I understand correctly, this deletes bookmarks older than x days, but when the newest bookmark is older than x days, it will get deleted and there are no bookmarks at all left? |
just tried by manually increasing date, yes it does. |
I edited this line, which now leaves additional 25 bookmarks. Feel free to change to any number you like.
|
as syncoid may use bookmarks for transfer, they pile up on the source host after a while and for example show up when doing "zfs get compression" and look exactly like a snapshot there. this may confuse users who don't know about bookmarks.
what about adding a prune config option to sanoid to also prune bookmarks, if you don't want tens of thousands of them? yes, you want to keep those, but you don't want tens of thousands to pile up until something blows/overflows
also see #618 and #544
The text was updated successfully, but these errors were encountered: