Skip to content

stored: fix not counting files correctly in mac jobs when autoxflate is enabled#1745

Merged
BareosBot merged 8 commits intobareos:masterfrom
sebsura:dev/ssura/master/fix-mistake
Mar 27, 2024
Merged

stored: fix not counting files correctly in mac jobs when autoxflate is enabled#1745
BareosBot merged 8 commits intobareos:masterfrom
sebsura:dev/ssura/master/fix-mistake

Conversation

@sebsura
Copy link
Contributor

@sebsura sebsura commented Mar 25, 2024

Thank you for contributing to the Bareos Project!

This PR fixes a bug that causes the sd to miscount the number of files during a internal mac job, if autoxflate is enabled.
The basic problem is that the VSId & VSTime are not reset correctly in the callback in that case, leading to splitting up files on block boundaries (i.e. 1 file becomes 2, if split on blocks), because the ReadRecords() routine thinks that we start reading data from a different job.

Also fixes a mistake in the last msgchan refactor that leads stops all sd<>sd jobs that take more than 30 seconds.

Please check

  • Short description and the purpose of this PR is present above this paragraph
  • Your name is present in the AUTHORS file (optional)

If you have any questions or problems, please give a comment in the PR.

Helpful documentation and best practices

Checklist for the reviewer of the PR (will be processed by the Bareos team)

Make sure you check/merge the PR using devtools/pr-tool to have some simple automated checks run and a proper changelog record added.

General
  • Is the PR title usable as CHANGELOG entry?
  • Purpose of the PR is understood
  • Commit descriptions are understandable and well formatted
  • Check backport line
  • Required backport PRs have been created
Source code quality
  • Source code changes are understandable
  • Variable and function names are meaningful
  • Code comments are correct (logically and spelling)
  • Required documentation changes are present and part of the PR

sebsura added 6 commits March 25, 2024 09:51
It should only start once the job was canceled and not once the job
was started ...
The socket may be closed if the job was canceled in an unfortunate
moment, which currently causes the sd to crash.  Instead we should
just log this and go on normally.
@pstorz pstorz self-requested a review March 27, 2024 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants