diff options
author | Lars Wirzenius <liw@liw.fi> | 2014-02-19 20:47:45 +0000 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2014-02-19 20:47:45 +0000 |
commit | 070d82a5b4f19926c5820cf0c451c3beefc56607 (patch) | |
tree | a669b4218318177eedf6be515087720eb6a455eb /yarns/0070-compression.yarn | |
parent | b24aaaaf867b7fa506bf3ba6884e2c3b52ba56e9 (diff) | |
download | obnam-070d82a5b4f19926c5820cf0c451c3beefc56607.tar.gz |
Convert tests/compression.script to yarn
Diffstat (limited to 'yarns/0070-compression.yarn')
-rw-r--r-- | yarns/0070-compression.yarn | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/yarns/0070-compression.yarn b/yarns/0070-compression.yarn new file mode 100644 index 00000000..bf7976ee --- /dev/null +++ b/yarns/0070-compression.yarn @@ -0,0 +1,29 @@ +Compressed repositories +======================= + +Compressed backups should work just like normal ones, except with all +the data written to the repository being compressed. We thus repeat a +basic backup test, but with compression. + + SCENARIO backup simple data using compression + GIVEN 100kB of new data in directory L + AND a manifest of L in M + AND user U sets configuration compress-with to deflate + WHEN user U backs up directory L to repository R + AND user U restores their latest generation in repository R into X + THEN L, restored to X, matches manifest M + AND user U can fsck the repository R + +If this works, everything else should work as well: by the time Obnam +writes anything to the repository, it has lost its sparseness, or +other special filesystem characteristics, and it's just B-tree nodes +or chunk data. + +It should be possible to restore from a compressed repository, even +without turning compression on. We continue the test scenario +accordingly. + + GIVEN user U sets configuration compress-with to none + WHEN user U restores their latest generation in repository R into Y + THEN L, restored to Y, matches manifest M + AND user U can fsck the repository R |