What to try first
- Confirm you opened the intended workspace.
- Confirm the space name is valid and already exists.
- Retry after the current operation finishes (or close other Rinne instances).
- If integrity is mentioned, run verify. If cleanup or staged trash is mentioned, run gc.
- If it’s an OS error, check permissions and free disk space.
Errors are part of normal operation — Rinne stops early when it can’t guarantee a correct result. It prints a clear message and exits with a non-zero code so you can fix the cause and retry safely.
Rinne does not guess or auto-create state on failure. For example, a missing space stays an error — you create and manage spaces explicitly so history remains predictable.
Common causes
- Workspace not opened / workspace not found
- You’re outside the intended workspace, or required workspace metadata is missing.
- Space not found
- The specified space does not exist (Rinne won’t create it automatically).
- Busy / locked
- Another operation is running, or a lock is held.
- Ignored by rinneignore
- The selected file or directory is excluded by
rinneignore.json, so a scoped save cannot include it. - Permission / path issues
- Access denied, read-only files, or OS path limitations.
- Storage / I/O errors
- Disk full, device errors, unstable drives, or interrupted reads.
- Integrity problems
- Verification failed, or snapshot metadata / stored content could not be validated.
Reporting
If you’re stuck, include the full error message and the exact command line when reporting an issue.
Early Access note: messages and codes may evolve as Rinne adds features. The principle stays the same: stop early when correctness can’t be guaranteed.