Hello, something appears to be wrong when using an NTFS filesystem as an aufs branch. I have been able to narrow it down to this test case: $ cd /tmp $ dd if=/dev/zero of=ntfs.img count=20480 $ mkfs.ntfs -F ntfs.img $ mkdir ntfs aufs $ sudo mount ntfs.img -o permissions,acl ntfs $ sudo mount -t aufs -o br:ntfs none aufs $ cd aufs $ git clone git://[1]git.code.sf.net/p/aufs/aufs3-standalone Cloning into 'aufs3-standalone'... fatal: Unable to create temporary file '/tmp/aufs/aufs3-standalone/.git/objects/pack/tmp_pack_XXXXXX':Permission denied fatal: index-pack failed $ ls ls: cannot open directory .: Stale NFS file handle $ cd .. $ sudo umount aufs /sbin/umount.aufs:proc_mnt.c:96: aufs: Invalid argument I'm not sure what the role of git is, but a simple "touch newfile" etc. in its place works perfectly. Either mounting the ntfs volume without the acl option or using "sudo git clone" result in cloning completing successfully, and subsequent "ls" will not raise ESTALE. However, when now removing the freshly cloned directory, the following will happen: $ sudo rm -r aufs3-standalone rm: cannot remove 'aufs3-standalone/.git/logs/refs/remotes': No such file or directory rm: cannot remove 'aufs3-standalone/.git/refs/remotes': No such file or directory $ sudo rm -r aufs3-standalone rm: cannot remove 'aufs3-standalone/.git/refs': No such file or directory $ sudo rm -r aufs3-standalone $ cd .. $ sudo umount aufs umount: aufs: Stale NFS file handle (yes, that's three times the same "rm -r" in direct succession, progressively raising less errors until it completes.) I'm using Linux Mint 16 (an Ubuntu derivative), which comes with kernel 3.11.0-12-generic and aufs 3.x-rcN-20130902. Can anyone reproduce this? Peter
References 1. http://git.code.sf.net/p/aufs/aufs3-standalone
------------------------------------------------------------------------------
