Skip to content
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

.bs files automatic removal #72

Open
feuerball11 opened this issue Jun 12, 2020 · 2 comments
Open

.bs files automatic removal #72

feuerball11 opened this issue Jun 12, 2020 · 2 comments

Comments

@feuerball11
Copy link

Hi,

i recently installed buttersink in an automated process to sync up snapper snapshots over ssh to another server as backup.

I now found that in every snapshot folder (.snappshots/xxx/) is now a .bs file. In itself that's not a problem, but it causes snapper to not delete the snapshot folder when it cleans up not needed timeline snapshots. So that an folder with the .bs file remains, and my .snapshots folder is filled up with these "useless" folders. At a timeline with hourly snapshots these will become a huge folder very quickly. would it be possible to clean up these .bs files automatically, so I don't end up with a folder containing million subfolders with .bs files in them?

Kind regards, Ignatz

@AmesCornish
Copy link
Owner

AmesCornish commented Jun 12, 2020 via email

@feuerball11
Copy link
Author

The process that deletes the snapshots is snapper. its its own program and I don't think I can convince it to delete the .bs files. At the end of the day I probably need to write my own script, running after buttersink.

it would be helpful if butersink had an option to automatically delete the .bs files, or don't even make them in the beginning. i don't have a problem with the process being slow, its automated between two server, running at night time.

so just being able to shut off the creating of the bs files would save ma a lot of time, figuring out how to find and delete all the .bs files after running buttersink.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants