<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/Documentation/duplicate-inodes.txt, branch xattr_user_buffer</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2017-11-12T19:06:13+00:00</updated>
<entry>
<title>main: add "-sharedstorage" flag</title>
<updated>2017-11-12T19:06:13+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-11-12T19:06:13+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=e36a0ebf189a826aaa63909c5518c16356f5f903'/>
<id>urn:sha1:e36a0ebf189a826aaa63909c5518c16356f5f903</id>
<content type='text'>
At the moment, it does two things:

1. Disable stat() caching so changes to the backing storage show up
   immediately.
2. Disable hard link tracking, as the inode numbers on the backing
   storage are not stable when files are deleted and re-created behind
   our back. This would otherwise produce strange "file does not exist"
   and other errors.

Mitigates https://github.com/rfjakob/gocryptfs/issues/156
</content>
</entry>
</feed>
