diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-11-22 18:20:55 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-11-22 18:21:28 -0400 |
| commit | 75a590bdd893e579c5e375e5ad797022f5847496 (patch) | |
| tree | 38c2e9f62d05b811ca025ba604a9898913dfdcb7 /doc | |
| parent | fd81b5047b314ecc96b34e0c9f017f8f5a62f072 (diff) | |
Put a workaround in the directory special remote for strange behavior with VFAT filesystems on Linux (mounted with shortname=mixed)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn | 23 |
1 files changed, 20 insertions, 3 deletions
diff --git a/doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn b/doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn index b686304e5..ae653d619 100644 --- a/doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn +++ b/doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn @@ -18,11 +18,28 @@ I wonder if the directory remote should use hashDirLower instead of hashDirMixed > git-annex intentionally uses the same layout for directory and rsync > special remotes as it does for the .git/annex directory. As far -> as I know it works ok on case-insensative filesystems. +> as I know it works ok on (truely) case-insensative filesystems. > > Based on your strace, if you `ls /media/annex/Zp`, you will see > "No such file or directory", but if you `mkdir /media/annex/Zp` it will > fail with "File exists". Doesn't make much sense to me. > -> I cannot reproduce this problem using a vfat filesystem -> mounted using the same options you show (linux 3.0.0). --[[Joey]] +> The (default) VFAT mount option shortname=mixed causes this behavior. +> With shortname=lower it works ok. --[[Joey]] +> +>> So, the options for fixing this bug seem to be to fix Linux (which would +>> be a good idea IMHO but I don't really want to go there), or generally +>> convert git-annex to using lowercase for its hashing (which would be a +>> large amount of pain to rewrite all the symlinks in every git repo), +>> or some special hack around this problem. +>> +>> I've put in a workaround for the problem in the directory special +>> remote; it will use mixed case but fall-back to lowercase as necessary. +>> +>> That does leave the case of a bare git repository with annexed content +>> stored on VFAT. More special casing could fix it, but that is, I +>> think, an unusual configuration. Leaving the bug open for that case, +>> and for the even more unlikely configuration of a rsync special remote +>> stored on VFAT. --[[Joey]] + +[[!meta title="bare git repository not supported on VFAT"]] |