summaryrefslogtreecommitdiff
path: root/obnam.md
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2021-03-12 11:12:46 +0200
committerLars Wirzenius <liw@liw.fi>2021-03-12 12:00:00 +0200
commit0fcb8f314a054e4c92e49461f1ae2d9392756638 (patch)
tree9d1690d3e4b23217a65412342de160c2dac49d48 /obnam.md
parent77e293e36d741a7f6e318672061d522d9dc35f6b (diff)
downloadobnam2-0fcb8f314a054e4c92e49461f1ae2d9392756638.tar.gz
feat: show warnings for any problems backing up files
Previously, we either ignored it or aborted the backup. Neither is good. Now we ignore the problem, except to show a warning at the end of the backup run.
Diffstat (limited to 'obnam.md')
-rw-r--r--obnam.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/obnam.md b/obnam.md
index bfaff5d..cffd83a 100644
--- a/obnam.md
+++ b/obnam.md
@@ -1430,6 +1430,25 @@ then file live/data.dat is restored to rest
then file live/bad.dat is not restored to rest
~~~
+## Unreadable directory
+
+This scenario verifies that Obnam will skip a file in a directory it
+can't read. Obnam should warn about that, but not give an error.
+
+~~~scenario
+given an installed obnam
+and a running chunk server
+and a client config based on smoke.yaml
+and a file live/unreadable/data.dat containing some random data
+and file live/unreadable has mode 000
+when I run obnam --config smoke.yaml backup
+then stdout contains "live/unreadable"
+then backup generation is GEN
+when I invoke obnam --config smoke.yaml restore <GEN> rest
+then file live/unreadable is restored to rest
+then file live/unreadable/data.dat is not restored to rest
+~~~
+
## Restore latest generation
This scenario verifies that the latest backup generation can be