Julius Plenz

ad 1., just considering the possibility – We have no clue about what happens to a file after we close the fd. We might be right in most cases by...

> If the user calls close(), we should indeed close it and not keep stale fds. FWIW: We could close it upon user request, but just before that use `fcntl`...

> I needed to verify that a certain system call works as expected and > think things through in terms of complexity, downsides etc. > Essentially your last comment is...

@hhoffstaette Any new developments on your part? How would you think about a simple option that’ll just disable calling `fsync()`?

> And the change to POSIX_FADV_NOREUSE instead of POSIX_FADV_DONTNEED. On the server rsync reads files only once. AFAICS, this would make the _semantics_ correct, and that’s what `nocache` is also...

This would need further changes in the documentation and the wrapper script. @onlyjob, what do you think about the general idea? Personally, I think the “lib” prefix is misleading, since...

This is an issue related to file metadata. `nocache` works on the content level, i.e. when reading or writing to the file. If you use `find`, `nocache` will have no...

I disagree. File metadata caching is really useful almost always and takes up very little memory, I would think.

Ok, I see your point. Actually I have no idea how to prevent metadata caching (or discard the data after use), but I’ll have a look at it some time...

From a quick read over the Kernel source I think it’s not easily possible. The best hint is still `fs/drop_caches.c`. Since ``` echo 2 > /proc/sys/vm/drop_caches # free dentries and...