-
-
Notifications
You must be signed in to change notification settings - Fork 758
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
exclude big files? #902
Comments
No (not yet?). See also: jborg/attic#330 |
ok I assume it is not on roadmap list? |
it has not been assigned to a milestone yet. if you want to help, you could try the workaround suggested in the linked ticket. |
This would be a good place to use --files-from (on my phone and can't find the ticket #, but it's been discussed recently). |
The solution linked in the ticket obviously works. However, I'd rather have all the excluded files directive at one single place, and it's quite uneasy to have to run another process and rely on a temporary file before running borg. (also, the find -size syntax is quite clumsy, for example try find /home -size -1M ...). I have a small 50 lines patch that extends patterns.py and adds the possibility to exclude files based on filesize and optionnally file extension. If anybody is interested, I can add tests for this new directive, and forward the diff to the mailing list. |
Picking this back up because I have another slightly different use case (→ #3097). The workaround will cause a significant performance penalty on anything beyond tiny datasets (anything larger than your RAM, I'd guess) and, more importantly. introduces a race condition between generating the file list and actually processing the files. We're already looking at the files' I'd vote for using the same option names and syntax as |
Thx for assiging this to a milestone, looking forward to it! |
superseded by #4102. |
Is there a way to exclude big files (bigger/smaller --than-size) with borg create?
The text was updated successfully, but these errors were encountered: