You can git annex fsck -q and it’ll hash all the files and tell you which files don’t match their hash. Rsync means your file got there intact, but rsync doesn’t safeguard against bit rot. While I do have a “master” disk, that is just a naming convention, git annex is just as distributed as git itself.įile hashing comes free. They’re all configured to talk to one another. On the flip side of that, when one of my drives start to get full, I can git annex drop file.ext (which considers annex.numcopies) then it removes the file from the repo, freeing space on the disk. I don’t have to manage that manually, it is done for me. Currently that is set at 3, so there are at least 3 copies of my files. I can use annex.numcopies to specify a minimum redundancy number for my files. Git annex repos are aware of one another, git annex whereis file.ext returns a list of repos that contain the file. There are several advantages of git-annex over an rsync solution. Git annex also supports metadata and can show and hide files based on that metadata. Darktable does have some nice lua scripting capability. I’m not sure if’d I’d call a hook from my editor or just do it on the CLI. That looks like it’ll work well too, but I’m super conservative when changing my workflow. Since git-annex can be used in tandem with regular git, I’m currently evaluating committing my metadata sidecar files (.xmp and. Read-only RAW files has been working well for me, I can’t accidentally delete them or otherwise mangle the file and RAW files really only need to be read anyway (not write or execute). With git-annex, I’m only using it for my RAW files, so they only get committed once upon import and git-annex makes them read-only by default. Does SSD count as a different medium from HDD? I somehow doubt itĭo you make commits with every photo edit? I still don’t have them on different medium and haven’t found a good way to do such a thing my current thinking is just making multi-part tar.7z files, then burning them to DVD. I was trying to follow the 3-2-1 backup strategy at first, but once I got going with git-annex, I realized that I could just add drives indiscriminately to my backup/parity routine… so I did. I’ll then start darktable or rawtherapee, both of which are pointed at the git annex raw file repo.įor many of the reasons listed below, but mostly I wanted to be able to take a drive full of my encrypted data off-site, not worry about adding data, then rotate the off-site data back to my apartment, updated it, then rotate it out again. I usually import then sync to at least one other drive for redundancy. Run git-annex sync -content to sync up content to all the connected drives. Plug in other git annex external drives and mount them. Run git commit -m “some message” to commit the changes to my git annex repo. Run exiftool script that renames files by their creation date and copies them into a date stamped folder in my git-annex raw files repoĬhange directory into the git-annex raw files repo Three of them are unencrypted and stay in my apartment, the other three are gpg encrypted and get rotated off site.Ĭhange directory into the camera medium directory I have six external hard drives that hold my git-annex repos. Advice needed: Pro photographer workflow on linux
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |