Skip to content

fix: Remove comment about locking #140

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.

Sign up for GitHub

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

Merged
aawsome merged 1 commit into from
May 23, 2026
Merged

fix: Remove comment about locking #140

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions src/commands/forget/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,8 @@ commands need to be called in sequence: `forget` to remove snapshots, and
snapshots. The latter can be automated with the `--prune` option of `forget`,
which runs `prune` automatically if any snapshots were actually removed.

Pruning snapshots can be a time-consuming process, depending on the number of
snapshots and data to process. During a prune operation, the repository is
locked and backups cannot be completed. Please plan your pruning so that there's
time to complete it and it doesn't interfere with regular backup runs.

It is advisable to run `rustic check` after pruning, to make sure you are
alerted, should the internal data structures of the repository be damaged.
alerted, should the internal data structures of the repository be damaged. But
note: If you run a `backup` parallel to this `check` command, the output may
produce some warnings as `check` cannote distinguish whether it's a running
`backup` and OK or an aborted backup with left-overs.
Loading