From ccf4af9229a6ce78a5c7a7b5b5fd1d7abfb4a6c9 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/5j.FKrMpxZS.luSB.5ahyosMU6RcaYq2#74c60" Date: Sat, 27 Jun 2015 21:22:20 +0000 Subject: [PATCH] --- doc/forum/Storing_copies_on_LTO_tapes__63__.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/forum/Storing_copies_on_LTO_tapes__63__.mdwn b/doc/forum/Storing_copies_on_LTO_tapes__63__.mdwn index 317ffc6cb9..175bc2b4ce 100644 --- a/doc/forum/Storing_copies_on_LTO_tapes__63__.mdwn +++ b/doc/forum/Storing_copies_on_LTO_tapes__63__.mdwn @@ -6,8 +6,8 @@ Three alternatives I've come up with so far: 1. Simply tar the repositories from the HDs to the tapes. Problem: no way to notify git annex of the existence of these manual copies. Or is there? 2. Remote (special or normal) on LTFS (linear posix compatible file system on top of tape). Problems: - 1. **git annex get**ing a dropped directory from there would cause files to be accessed in random order, right? Or is the retrieve guaranteed to happen in the same order as the files in the directory were written by **git annex copy**? + 1. `git annex get`ing a dropped directory from there would cause files to be accessed in random order, right? Or is the retrieve guaranteed to happen in the same order as the files in the directory were written by `git annex copy`? 2. LTFS has a big block size (512KB) => wasted space when lots of small files. (Not a major problem, though.) -3. Write a special (read-only) remote hook for *tar*. Problem: **get** would make one *RETRIEVE* request per file, leading to random access again, while the only effective way would be to get a list of all files to be retrieved, and then returning them in the order they turn up from the tar package (or even ingest the whole tar file to .git/annex/). +3. Write a special (read-only) remote hook for `tar`. Problem: `git annex get` would make one hook *RETRIEVE* request per file, leading to random access again, while the only effective way would be to get a list of all files to be retrieved, and then returning them in the order they turn up from the tar package (or even ingest the whole tar file to .git/annex/). Thoughts?