mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

response; cannot reproduce

Browse source
This commit is contained in:
Joey Hess 2011-11-22 12:37:51 -04:00
parent d1ecd381c9
commit fc2f0e8b1a
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/bugs/directory_remote_and_case_sensitivity_on_FAT.mdwn
View file

@ -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]]