ACM Home Page
Please provide us with feedback. Feedback
Using model checking to find serious file system errors
Full text PdfPdf (534 KB)
Source ACM Transactions on Computer Systems (TOCS) archive
Volume 24 ,  Issue 4  (November 2006) table of contents
Pages: 393 - 423  
Year of Publication: 2006
ISSN:0734-2071
Authors
Junfeng Yang  Stanford University, Stanford, CA
Paul Twohey  Stanford University, Stanford, CA
Dawson Engler  Stanford University, Stanford, CA
Madanlal Musuvathi  Microsoft Research, Redmond, WA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 22,   Downloads (12 Months): 130,   Citation Count: 6
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1189256.1189259
What is a DOI?

ABSTRACT

This article shows how to use model checking to find serious errors in file systems. Model checking is a formal verification technique tuned for finding corner-case errors by comprehensively exploring the state spaces defined by a system. File systems have two dynamics that make them attractive for such an approach. First, their errors are some of the most serious, since they can destroy persistent data and lead to unrecoverable corruption. Second, traditional testing needs an impractical, exponential number of test cases to check that the system will recover if it crashes at any point during execution. Model checking employs a variety of state-reducing techniques that allow it to explore such vast state spaces efficiently.We built a system, FiSC, for model checking file systems. We applied it to four widely-used, heavily-tested file systems: ext3, JFS, ReiserFS and XFS. We found serious bugs in all of them, 33 in total. Most have led to patches within a day of diagnosis. For each file system, FiSC found demonstrable events leading to the unrecoverable destruction of metadata and entire directories, including the file system root directory “/”.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Arkoudas, K., Zee, K., Kuncak, V., and Rinard, M. 2004. On verifying a file system implementation. Tech. Rep. 946, MIT CSAIL. May.
 
2
3
 
4
 
5
 
6
7
 
8
Coverity. http://coverity.com. SWAT: the Coverity software analysis toolset.
9
10
 
11
 
12
Engler, D., Chelf, B., Chou, A., and Hallem, S. 2000. Checking system rules using system-specific, programmer-written compiler extensions. In Proceedings of Operating Systems Design and Implementation (OSDI).
 
13
Engler, D. and Musuvathi, M. 2004. Static analysis versus software model checking for bug finding. In Invited paper: Fifth International Conference on Verification, Model Checking, and Abstract Interpretation (VMCAI04). 191--210.
 
14
ext2/ext3. http://e2fsprogs.sourceforge.net. The ext2/ext3 file system.
15
16
17
 
18
Ganger, G. R. and Patt., Y. N. 1995. Soft updates: A solution to the metadata update problem in file systems. Tech. rep., University of Michigan.
19
 
20
 
21
 
22
JFS. http://www-124.ibm.com/jfs. The IBM journaling file system for linux.
 
23
K., M. 1993. Symbolic Model Checking. Kluwer Academic Publishers.
24
 
25
 
26
LTP. http://ltp.sourceforge.net. The linux test project.
 
27
Musuvathi, M. and Engler, D. R. 2004. Model checking large network protocol implementations. In Proceedings of the First Symposium on Networked Systems Design and Implementation.
28
29
 
30
ReiserFS. http://www.namesys.com. The ReiserFS file system.
 
31
Sandberg, R., Goldberg, D., Kleiman, S., Walsh, and Lyon, B. 1985. Design and implementation of the Sun network file system. In Proceedings of the Summer USENIX Conference (Sum). 119--130.
 
32
 
33
stress. http://weather.ou.edu/~apw/projects/stress. A file system stress testing tool.
34
 
35
XFS. http://oss.sgi.com/projects/xfs. A high-performance journaling filesystem.
 
36
Yang, J., Sar, C., and Engler, D. 2006. Explode: A lightweight, general system for finding serious errors in storage systems. In Proceedings of the Seventh Symposium on Operating Systems Design and Implementation.


Collaborative Colleagues:
Junfeng Yang: colleagues
Paul Twohey: colleagues
Dawson Engler: colleagues
Madanlal Musuvathi: colleagues