Hi,
There is something I need to make sure.
Are you using fuse-based NTFS or in-kernel (native) NTFS?
Where can I get the source files of it?
I am using the ntfs-3g driver, which as far as I know is fuse-based (but I'm
not all that kernel-savvy). The source seems to be located at
[1]http://www.tuxera.com/community/ntfs-3g-download/, however I'm also using
a distributor-supplied (and preinstalled) version. I have, unfortunately,
never compiled a kernel from source, though I've been thinking of setting up
a testing environment for exactly such cases, so I might look into that next
week.
Honestly speaking, I don't have tried CONFIG_NTFS_RW=y for a long time.
Is it reliably working now?
For example, "git clone" issues link(2) systemcall. Does your NTFS
support it?
While the option "acl" may be related, I need to make sure which version
of NTFS are you using.
I haven't had any problems with the ntfs-3g driver over the past few years.
AFAIK, it supports both hard- and softlinks; anyway, git * has always worked
for me on ntfs drives.
I have meanwhile found out it may have something to do with git creating
files with read-only permission (0444). Sometimes manually creating such a
file will also result in ENOPERM followed by ESTALE, and I've seen an empty
file with 0400 permissions being created instead. I however haven't been
able to consistently reproduce this; I'll have to look into that again
later.
Anyway I'd suggest you to make sure that your distributor does NOT make
any changes to aufs, otherwise I cannot support your version.
I thought so. I'll try to find out where the source for my version is
located and check. In any case, I probably should also raise this with the
distribution developers.
Peter Kork
References
1. http://www.tuxera.com/community/ntfs-3g-download/
------------------------------------------------------------------------------