The Experts below are selected from a list of 42 Experts worldwide ranked by ideXlab platform
Vijay Chidambaram - One of the best experts on this subject based on the ideXlab platform.
-
CrashMonkey and ACE: Systematically Testing File-System Crash Consistency
ACM Transactions on Storage, 2019Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present CrashMonkey and Ace, a set of tools to Systematically find crash-consistency bugs in Linux File Systems. CrashMonkey is a record-and-replay framework which tests a given workload on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. Ace automatically generates all the workloads to be run on the Target File System. We build CrashMonkey and Ace based on a new approach to test File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last 5 years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly created File System, and that all reported bugs result from crashes after fsync()-related System calls. CrashMonkey and Ace are able to find 24 out of the 26 crash-consistency bugs reported in the last 5 years. Our tools also revealed 10 new crash-consistency bugs in widely used, mature Linux File Systems, 7 of which existed in the kernel since 2014. Additionally, our tools found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity, loss of persisted Files and directories, and data loss.
-
OSDI - Finding crash-consistency bugs with bounded black-box crash testing
2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CRASHMONKEY and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
-
Finding Crash-Consistency Bugs with Bounded Black-Box Crash Testing
arXiv: Operating Systems, 2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CrashMonkey and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. Our tools also found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
Jayashree Mohan - One of the best experts on this subject based on the ideXlab platform.
-
CrashMonkey and ACE: Systematically Testing File-System Crash Consistency
ACM Transactions on Storage, 2019Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present CrashMonkey and Ace, a set of tools to Systematically find crash-consistency bugs in Linux File Systems. CrashMonkey is a record-and-replay framework which tests a given workload on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. Ace automatically generates all the workloads to be run on the Target File System. We build CrashMonkey and Ace based on a new approach to test File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last 5 years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly created File System, and that all reported bugs result from crashes after fsync()-related System calls. CrashMonkey and Ace are able to find 24 out of the 26 crash-consistency bugs reported in the last 5 years. Our tools also revealed 10 new crash-consistency bugs in widely used, mature Linux File Systems, 7 of which existed in the kernel since 2014. Additionally, our tools found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity, loss of persisted Files and directories, and data loss.
-
OSDI - Finding crash-consistency bugs with bounded black-box crash testing
2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CRASHMONKEY and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
-
Finding Crash-Consistency Bugs with Bounded Black-Box Crash Testing
arXiv: Operating Systems, 2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CrashMonkey and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. Our tools also found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
Ian Foster - One of the best experts on this subject based on the ideXlab platform.
-
CLUSTER - FSMonitor: Scalable File System Monitoring for Arbitrary Storage Systems
2019 IEEE International Conference on Cluster Computing (CLUSTER), 2019Co-Authors: Arnab K. Paul, Ryan Chard, Kyle Chard, Steven Tuecke, Ali R. Butt, Ian FosterAbstract:Data automation, monitoring, and management tools are reliant on being able to detect, report, and respond to File System events. Various data event reporting tools exist for specific operating Systems and storage devices, such as inotify for Linux, kqueue for BSD, and FSEvents for macOS. However, these tools are not designed to monitor distributed File Systems. Indeed, many cannot scale to monitor many thousands of directories, or simply cannot be applied to distributed File Systems. Moreover, each tool implements a custom API and event representation, making the development of generalized and portable event-based applications challenging. As File Systems grow in size and become increasingly diverse, there is a need for scalable monitoring solutions that can be applied to a wide range of both distributed and local Systems. We present here a generic and scalable File System monitor and event reporting tool, FSMonitor, that provides a File-System-independent event representation and event capture interface. FSMonitor uses a modular Data Storage Interface (DSI) architecture to enable the selection and application of appropriate event monitoring tools to detect and report events from a Target File System, and implements efficient and fault-tolerant mechanisms that can detect and report events even on large File Systems. We describe and evaluate DSIs for common UNIX, macOS, and Windows storage Systems, and for the Lustre distributed File System. Our experiments on a 897 TB Lustre File System show that FSMonitor can capture and process almost 38 000 events per second.
-
FSMonitor: Scalable File System Monitoring for Arbitrary Storage Systems
2019 IEEE International Conference on Cluster Computing (CLUSTER), 2019Co-Authors: Arnab K. Paul, Ryan Chard, Kyle Chard, Steven Tuecke, Ali R. Butt, Ian FosterAbstract:Data automation, monitoring, and management tools are reliant on being able to detect, report, and respond to File System events. Various data event reporting tools exist for specific operating Systems and storage devices, such as inotify for Linux, kqueue for BSD, and FSEvents for macOS. However, these tools are not designed to monitor distributed File Systems. Indeed, many cannot scale to monitor many thousands of directories, or simply cannot be applied to distributed File Systems. Moreover, each tool implements a custom API and event representation, making the development of generalized and portable event-based applications challenging. As File Systems grow in size and become increasingly diverse, there is a need for scalable monitoring solutions that can be applied to a wide range of both distributed and local Systems. We present here a generic and scalable File System monitor and event reporting tool, FSMonitor, that provides a File-System-independent event representation and event capture interface. FSMonitor uses a modular Data Storage Interface (DSI) architecture to enable the selection and application of appropriate event monitoring tools to detect and report events from a Target File System, and implements efficient and fault-tolerant mechanisms that can detect and report events even on large File Systems. We describe and evaluate DSIs for common UNIX, macOS, and Windows storage Systems, and for the Lustre distributed File System. Our experiments on a 897 TB Lustre File System show that FSMonitor can capture and process almost 38 000 events per second.
Ashlie Martinez - One of the best experts on this subject based on the ideXlab platform.
-
CrashMonkey and ACE: Systematically Testing File-System Crash Consistency
ACM Transactions on Storage, 2019Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present CrashMonkey and Ace, a set of tools to Systematically find crash-consistency bugs in Linux File Systems. CrashMonkey is a record-and-replay framework which tests a given workload on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. Ace automatically generates all the workloads to be run on the Target File System. We build CrashMonkey and Ace based on a new approach to test File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last 5 years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly created File System, and that all reported bugs result from crashes after fsync()-related System calls. CrashMonkey and Ace are able to find 24 out of the 26 crash-consistency bugs reported in the last 5 years. Our tools also revealed 10 new crash-consistency bugs in widely used, mature Linux File Systems, 7 of which existed in the kernel since 2014. Additionally, our tools found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity, loss of persisted Files and directories, and data loss.
-
OSDI - Finding crash-consistency bugs with bounded black-box crash testing
2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CRASHMONKEY and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
-
Finding Crash-Consistency Bugs with Bounded Black-Box Crash Testing
arXiv: Operating Systems, 2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CrashMonkey and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. Our tools also found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
Pandian Raju - One of the best experts on this subject based on the ideXlab platform.
-
CrashMonkey and ACE: Systematically Testing File-System Crash Consistency
ACM Transactions on Storage, 2019Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present CrashMonkey and Ace, a set of tools to Systematically find crash-consistency bugs in Linux File Systems. CrashMonkey is a record-and-replay framework which tests a given workload on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. Ace automatically generates all the workloads to be run on the Target File System. We build CrashMonkey and Ace based on a new approach to test File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last 5 years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly created File System, and that all reported bugs result from crashes after fsync()-related System calls. CrashMonkey and Ace are able to find 24 out of the 26 crash-consistency bugs reported in the last 5 years. Our tools also revealed 10 new crash-consistency bugs in widely used, mature Linux File Systems, 7 of which existed in the kernel since 2014. Additionally, our tools found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity, loss of persisted Files and directories, and data loss.
-
OSDI - Finding crash-consistency bugs with bounded black-box crash testing
2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CRASHMONKEY and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
-
Finding Crash-Consistency Bugs with Bounded Black-Box Crash Testing
arXiv: Operating Systems, 2018Co-Authors: Jayashree Mohan, Ashlie Martinez, Soujanya Ponnapalli, Pandian Raju, Vijay ChidambaramAbstract:We present a new approach to testing File-System crash consistency: bounded black-box crash testing (B3). B3 tests the File System in a black-box manner using workloads of File-System operations. Since the space of possible workloads is infinite, B3 bounds this space based on parameters such as the number of File-System operations or which operations to include, and exhaustively generates workloads within this bounded space. Each workload is tested on the Target File System by simulating power-loss crashes while the workload is being executed, and checking if the File System recovers to a correct state after each crash. B3 builds upon insights derived from our study of crash-consistency bugs reported in Linux File Systems in the last five years. We observed that most reported bugs can be reproduced using small workloads of three or fewer File-System operations on a newly-created File System, and that all reported bugs result from crashes after fsync() related System calls. We build two tools, CrashMonkey and ACE, to demonstrate the effectiveness of this approach. Our tools are able to find 24 out of the 26 crash-consistency bugs reported in the last five years. Our tools also revealed 10 new crash-consistency bugs in widely-used, mature Linux File Systems, seven of which existed in the kernel since 2014. Our tools also found a crash-consistency bug in a verified File System, FSCQ. The new bugs result in severe consequences like broken rename atomicity and loss of persisted Files.
