Peter Kork: > 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
Just to make sure, your /etc/mtab has an entry such like this? fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/... /tmp/ntfs fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0 > 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. OK. I will try reproducing the problem and reading the source code to see what is happening. It will be the latest version of ntfs-3g, but I don't care for a while. When you find out the exact version you are using, please let me know. > 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. That is interesting. Did it happen on ntfs-3g, without aufs? J. R. Okajima ------------------------------------------------------------------------------
