diff options
author | https://launchpad.net/~stephane-gourichon-lpad <stephane-gourichon-lpad@web> | 2016-10-30 19:19:22 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2016-10-30 19:19:22 +0000 |
commit | df28c9a49c649b228dfcae47254cfaea60b32dde (patch) | |
tree | 7eee39e1d94b2a23bef7fc3cac653cd6d0ebab0b | |
parent | 6fcd64ee10a240045dec161f15eb67aef0c69243 (diff) |
Added a comment: Bitten again by "E" backend, wish "e" backend.
-rw-r--r-- | doc/walkthrough/renaming_files/comment_6_2ae2cc3dba5db4d4354a5b49c490272e._comment | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/walkthrough/renaming_files/comment_6_2ae2cc3dba5db4d4354a5b49c490272e._comment b/doc/walkthrough/renaming_files/comment_6_2ae2cc3dba5db4d4354a5b49c490272e._comment new file mode 100644 index 000000000..d6db35568 --- /dev/null +++ b/doc/walkthrough/renaming_files/comment_6_2ae2cc3dba5db4d4354a5b49c490272e._comment @@ -0,0 +1,32 @@ +[[!comment format=mdwn + username="https://launchpad.net/~stephane-gourichon-lpad" + nickname="stephane-gourichon-lpad" + avatar="http://cdn.libravatar.org/avatar/02d4a0af59175f9123720b4481d55a769ba954e20f6dd9b2792217d9fa0c6089" + subject="Bitten again by "E" backend, wish "e" backend." + date="2016-10-30T19:19:21Z" + content=""" +Changing file extension is arguably not a very common use case. But changing extension case is more common, especially when copying files from FAT filesystems through different ways (Card reader, plugging device directly), and causes troubles. + +# Concrete case + +A set of files were imported with extension NEF and JPG, by mistake (forgot to rename them first), using default (or is it?) backend SHA256E. + +When using `git annex reinject --known` to cleanup another copy, files were not detected as known. + +This will happen again and feels not very good. + +# Workaround + +Thanks to CandyAngel I know I can rename then use `git annex migrate --force` and `reinject` again. + +# Better solution + +A SHA256e backend (that squashes extensions to lowercase) would not have this problem. + +# Additional information + +Why not switch to plain SHA256 backend? I'm a little paranoid (which makes me a good fit for using git-annex overall). + +One of the reason I use git-annex is that its storage format is actually simple, and files can be accessed even on a computer that can read the plain filesystem, without git or git-annex required. But in the lifetime of a filesystem, many bad things can happen and details of storage format may make a difference in case of major recovery (or even sanity check) scenario. Hashes without extension feel somehow uncomfortable. Lowercase extension backends feel much better. + +"""]] |