News for hackers. Stuff that matters.
Re:Show HN: Goofys – a faster s3fs written in Go by rictic on Monday October 19, 2015 @12:58PM (#10414122)
I appreciate any project that makes its strengths and weaknesses very clear and documents its consistency semantics.

Reading around[1], it looks like close-to-open consistency means that all writes must be flushed before the close() call returns, and all subsequent open() calls to the file must see the changes. IO may otherwise be buffered or cached by the FS.

1] Best source I found were these lecture slides: http://www0.cs.ucl.ac.uk/staff/B.Karp/gz03/f2011/lectures/gz...

Re:Show HN: Goofys – a faster s3fs written in Go by khc on Monday October 19, 2015 @01:00PM (#10414135)
The caveat is that goofys is subjected to the underly S3, which if you are using Amazon is only eventually consistent (http://areweconsistentyet.com/)