Crash consistency

Rethinking the fundamental abstractions of the file system.

[1]  Francesco Zappa Nardelli,et al.  86-TSO : A Rigorous and Usable Programmer ’ s Model for x 86 Multiprocessors , 2010 .

[2]  Leslie Lamport,et al.  How to Make a Multiprocessor Computer That Correctly Executes Multiprocess Programs , 2016, IEEE Transactions on Computers.

[3]  Doug Terry,et al.  Replicated data consistency explained through baseball , 2013, CACM.

[4]  Eddie Kohler,et al.  Specifying Crash Safety for Storage Systems , 2015, HotOS.

[5]  Hairong Kuang,et al.  The Hadoop Distributed File System , 2010, 2010 IEEE 26th Symposium on Mass Storage Systems and Technologies (MSST).

[6]  Mark Lillibridge,et al.  Torturing Databases for Fun and Profit , 2014, OSDI.

[7]  Cristian Ungureanu,et al.  Revisiting storage for smartphones , 2012, TOS.

[8]  Yale N. Patt,et al.  Metadata update performance in file systems , 1994, OSDI '94.

[9]  Andrea C. Arpaci-Dusseau,et al.  Beyond Storage APIs: Provable Semantics for Storage Stacks , 2015, HotOS.

[10]  Andrea C. Arpaci-Dusseau,et al.  All File Systems Are Not Created Equal: On the Complexity of Crafting Crash-Consistent Applications , 2014, OSDI.

[11]  Robert B. Hagmann,et al.  Reimplementing the Cedar file system using logging and group commit , 1987, SOSP '87.

[12]  Terence Kelly,et al.  Failure-Atomic Updates of Application Data in a Linux File System , 2015, FAST.

[13]  David A. Wood,et al.  A Primer on Memory Consistency and Cache Coherence , 2012, Synthesis Lectures on Computer Architecture.