diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-11-22 12:37:51 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-11-22 12:37:51 -0400 |
| commit | fc2f0e8b1a4bd016ac29606381dfb7034c88e9f5 (patch) | |
| tree | 2e0c0d3d659e1c63bf47a9051c3fc858eb3c3651 | |
| parent | d1ecd381c97b07043bcaf0c40387b6fc6b9c7e56 (diff) | |
response; cannot reproduce
| -rw-r--r-- | doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn | 11 |
1 files changed, 11 insertions, 0 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 d1b21a9e7..b686304e5 100644 --- a/doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn +++ b/doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn @@ -15,3 +15,14 @@ The filesystem is FAT32 and has weird case semantics. This was mounted by udisk /dev/sdb1 on /media/annex type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec) 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. +> +> 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]] |