Instructions around data loss but meta data present #842
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#842
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://garagehq.deuxfleurs.fr/documentation/operations/recovering/
This list scenarios where if data is lost but meta data is still present and suggests to just to issue
garage repair -a --yes blocks
One challenge with these instructions is that garage refuses to come up in a empty data directory. It throws following error:
Error: Could not find expected marker file `garage-marker` in data directory `<location>`, make sure this data directory is mounted correctly.
Instructions need to be updated on how to start Garage in such scenario.