From ea66c489944aba58e82184cdefc831de752ad4c2 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Thu, 8 May 2008 18:42:58 +0000
Subject: [PATCH] add papers about failures of local filesystems

[Imported from Trac: page Bibliography, version 14]
---
 Bibliography.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/Bibliography.md b/Bibliography.md
index 72b584d..bca850a 100644
--- a/Bibliography.md
+++ b/Bibliography.md
@@ -23,7 +23,13 @@ Here are some papers that are potentially of interest.
 
 ## Local Filesystems
 
-[IRON Filesystems](https://www.cs.wisc.edu/wind/Publications/iron-sosp05.pdf) examines how ext3, reiserfs, xfs, and ntfs handle various sorts of errors
+Model-Based Failure Analysis of Journaling File Systems [citeseer](http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.78.8911) [PDF](http://www.cs.wisc.edu/wind/Publications/sfa-dsn05.pdf) compares ext3, reiserfs, and JFS under conditions of latent sector errors.  (Impatient people: read the Introduction and look at the table on page 9.)
+
+IRON Filesystems [citeseer](http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.66.3785) [PDF](https://www.cs.wisc.edu/wind/Publications/iron-sosp05.pdf), a follow-on by the authors of "Model-Based Failure Analysis of Journaling File Systems" examines how ext3, reiserfs, xfs, and ntfs handle various sorts of errors (impatient people, see table on page 8, "File System Summary" on page 9, and table on page 10).
+
+Using Model Checking to Find Serious File System Errors [citeseer](http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.80.8142) [PDF](https://www.stanford.edu/~engler/osdi04-fisc.pdf) analyzes ext3, JFS, and reiserfs (impatient: page 10).
+
+eXplode: A lightweight, general approach for finding serious errors in storage systems [PDF](https://www.stanford.edu/~engler/explode-osdi06.pdf), a follow-on by the authors of "Using Model Checking to Find Serious File System Errors", compares ext2, ext3, reiserfs, reiser4, jfs, xfs, msdos, vfat, hfs, and hfs+ to see if you sync them and then crash them if your allegedly synced data is actually recoverable (impatient: page 11)
 
 ## See Also