... | ... | @@ -9,7 +9,7 @@ Most of time for a project requester, it is perferred to access files directly i |
|
|
|
|
|
## Sample procedure
|
|
|
|
|
|
1. Init a git repository on the target file system, such as a USB harddisk.
|
|
|
* Init a git repository on the target file system, such as a USB harddisk.
|
|
|
|
|
|
```
|
|
|
hmei@Leon-LUMC:/media/hmei/3E4A-01AF$ mkdir annex
|
... | ... | @@ -29,7 +29,7 @@ ok |
|
|
(Recording state in git...)
|
|
|
```
|
|
|
|
|
|
2. Use the project folder as remote repository and sync it.
|
|
|
* Use the project folder as remote repository and sync it.
|
|
|
|
|
|
```
|
|
|
hmei@Leon-LUMC:/media/hmei/3E4A-01AF/annex$ git remote add laptop ~/git/source_test_annex/
|
... | ... | @@ -72,14 +72,14 @@ total 8 |
|
|
drwx------ 2 hmei hmei 4096 mrt 26 21:18 bam
|
|
|
```
|
|
|
|
|
|
3. Since the USB disk uses FAT, by default git-annex is using direct mode. Symlinks are stored as file content.
|
|
|
* Since the USB disk uses FAT, by default git-annex is using direct mode. Symlinks are stored as file content.
|
|
|
|
|
|
```
|
|
|
hmei@Leon-LUMC:/media/hmei/3E4A-01AF/annex$ cat cool_big.bam
|
|
|
.git/annex/objects/Mm/7V/SHA256E-s414416896--8480c5bf05b9e57663e231f6ce373ff17cf3f771f5ba2b6f63700b7287a6f2b4.bam/SHA256E-s414416896--8480c5bf05b9e57663e231f6ce373ff17cf3f771f5ba2b6f63700b7287a6f2b4.bamhmei@Leon-LUMC:/media/hmei/3E4A-01AF/annex$
|
|
|
```
|
|
|
|
|
|
4. Now we can get the actual files
|
|
|
* Now we can get the actual files
|
|
|
|
|
|
```
|
|
|
hmei@Leon-LUMC:/media/hmei/3E4A-01AF/annex$ git annex get .
|
... | ... | @@ -98,7 +98,7 @@ drwx------ 2 hmei hmei 4096 mrt 26 21:18 bam |
|
|
-rw-r--r-- 1 hmei hmei 414416896 mrt 26 21:18 cool_big.bam
|
|
|
```
|
|
|
|
|
|
5. Don't forget to check the file integrity of the entire repository.
|
|
|
* Don't forget to check the file integrity of the entire repository.
|
|
|
|
|
|
```
|
|
|
hmei@Leon-LUMC:/media/hmei/3E4A-01AF/annex$ git annex fsck
|
... | ... | |