summaryrefslogtreecommitdiff
path: root/obnam.md
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2021-02-07 17:46:06 +0200
committerLars Wirzenius <liw@liw.fi>2021-02-07 18:45:57 +0200
commit028fd279652dbe167b12b32dff00c6a299c4fc02 (patch)
tree4328795e0e96a493ef8e71ae29c81fc3e9811914 /obnam.md
parent3ef5bd7a3ab445509216116bb2f8009ace2b1080 (diff)
downloadobnam2-028fd279652dbe167b12b32dff00c6a299c4fc02.tar.gz
test: add scenario for live data file being unreadable
Diffstat (limited to 'obnam.md')
-rw-r--r--obnam.md22
1 files changed, 22 insertions, 0 deletions
diff --git a/obnam.md b/obnam.md
index 204d6d9..cb08f13 100644
--- a/obnam.md
+++ b/obnam.md
@@ -1269,6 +1269,28 @@ given a manifest of the directory live restored in rest in rest.yaml
then files live.yaml and rest.yaml match
~~~
+## Unreadable file
+
+This scenario verifies that Obnam will back up all files of live data,
+even if one of them is unreadable. By inference, we assume this means
+other errors on individual files also won't end the backup
+prematurely.
+
+
+~~~scenario
+given an installed obnam
+and a running chunk server
+and a client config based on smoke.yaml
+and a file live/data.dat containing some random data
+and a file live/bad.dat containing some random data
+and file live/bad.dat has mode 000
+when I run obnam --config smoke.yaml backup
+then backup generation is GEN
+when I invoke obnam --config smoke.yaml restore <GEN> rest
+then file live/data.dat is restored to rest
+then file live/bad.dat is not restored to rest
+~~~
+
## Restore latest generation
This scenario verifies that the latest backup generation can be