The Experts below are selected from a list of 90 Experts worldwide ranked by ideXlab platform
Andrew S Tanenbaum - One of the best experts on this subject based on the ideXlab platform.
-
transaction based process crash recovery of file System Namespace modules
Pacific Rim International Symposium on Dependable Computing, 2013Co-Authors: David C Van Moolenbroek, Raja Appuswamy, Andrew S TanenbaumAbstract:In this paper, we describe the emerging concept of Namespace modules: operating System components that are responsible for constructing a hierarchical file System Namespace based on one or more individual underlying file objects. We show that the likely presence of software bugs in such modules calls for the ability to recover from crashes, but that the current state of the art falls short of the desired behavior. We then introduce a crash recovery solution that is based on transactions, and detail the requirements for a System to implement this solution. We apply our solution to two different use cases: the primary Namespace module for a storage stack, and an extension module that exposes the contents of scientific data files. Our evaluation shows that the transaction System has low overhead and significantly adds to the robustness of the Namespace modules.
-
PRDC - Transaction-Based Process Crash Recovery of File System Namespace Modules
2013 IEEE 19th Pacific Rim International Symposium on Dependable Computing, 2013Co-Authors: David C Van Moolenbroek, Raja Appuswamy, Andrew S TanenbaumAbstract:In this paper, we describe the emerging concept of Namespace modules: operating System components that are responsible for constructing a hierarchical file System Namespace based on one or more individual underlying file objects. We show that the likely presence of software bugs in such modules calls for the ability to recover from crashes, but that the current state of the art falls short of the desired behavior. We then introduce a crash recovery solution that is based on transactions, and detail the requirements for a System to implement this solution. We apply our solution to two different use cases: the primary Namespace module for a storage stack, and an extension module that exposes the contents of scientific data files. Our evaluation shows that the transaction System has low overhead and significantly adds to the robustness of the Namespace modules.
David C Van Moolenbroek - One of the best experts on this subject based on the ideXlab platform.
-
transaction based process crash recovery of file System Namespace modules
Pacific Rim International Symposium on Dependable Computing, 2013Co-Authors: David C Van Moolenbroek, Raja Appuswamy, Andrew S TanenbaumAbstract:In this paper, we describe the emerging concept of Namespace modules: operating System components that are responsible for constructing a hierarchical file System Namespace based on one or more individual underlying file objects. We show that the likely presence of software bugs in such modules calls for the ability to recover from crashes, but that the current state of the art falls short of the desired behavior. We then introduce a crash recovery solution that is based on transactions, and detail the requirements for a System to implement this solution. We apply our solution to two different use cases: the primary Namespace module for a storage stack, and an extension module that exposes the contents of scientific data files. Our evaluation shows that the transaction System has low overhead and significantly adds to the robustness of the Namespace modules.
-
PRDC - Transaction-Based Process Crash Recovery of File System Namespace Modules
2013 IEEE 19th Pacific Rim International Symposium on Dependable Computing, 2013Co-Authors: David C Van Moolenbroek, Raja Appuswamy, Andrew S TanenbaumAbstract:In this paper, we describe the emerging concept of Namespace modules: operating System components that are responsible for constructing a hierarchical file System Namespace based on one or more individual underlying file objects. We show that the likely presence of software bugs in such modules calls for the ability to recover from crashes, but that the current state of the art falls short of the desired behavior. We then introduce a crash recovery solution that is based on transactions, and detail the requirements for a System to implement this solution. We apply our solution to two different use cases: the primary Namespace module for a storage stack, and an extension module that exposes the contents of scientific data files. Our evaluation shows that the transaction System has low overhead and significantly adds to the robustness of the Namespace modules.
Raja Appuswamy - One of the best experts on this subject based on the ideXlab platform.
-
transaction based process crash recovery of file System Namespace modules
Pacific Rim International Symposium on Dependable Computing, 2013Co-Authors: David C Van Moolenbroek, Raja Appuswamy, Andrew S TanenbaumAbstract:In this paper, we describe the emerging concept of Namespace modules: operating System components that are responsible for constructing a hierarchical file System Namespace based on one or more individual underlying file objects. We show that the likely presence of software bugs in such modules calls for the ability to recover from crashes, but that the current state of the art falls short of the desired behavior. We then introduce a crash recovery solution that is based on transactions, and detail the requirements for a System to implement this solution. We apply our solution to two different use cases: the primary Namespace module for a storage stack, and an extension module that exposes the contents of scientific data files. Our evaluation shows that the transaction System has low overhead and significantly adds to the robustness of the Namespace modules.
-
PRDC - Transaction-Based Process Crash Recovery of File System Namespace Modules
2013 IEEE 19th Pacific Rim International Symposium on Dependable Computing, 2013Co-Authors: David C Van Moolenbroek, Raja Appuswamy, Andrew S TanenbaumAbstract:In this paper, we describe the emerging concept of Namespace modules: operating System components that are responsible for constructing a hierarchical file System Namespace based on one or more individual underlying file objects. We show that the likely presence of software bugs in such modules calls for the ability to recover from crashes, but that the current state of the art falls short of the desired behavior. We then introduce a crash recovery solution that is based on transactions, and detail the requirements for a System to implement this solution. We apply our solution to two different use cases: the primary Namespace module for a storage stack, and an extension module that exposes the contents of scientific data files. Our evaluation shows that the transaction System has low overhead and significantly adds to the robustness of the Namespace modules.
A.l.n. Reddy - One of the best experts on this subject based on the ideXlab platform.
-
MVSS: an active storage architecture
IEEE Transactions on Parallel and Distributed Systems, 2003Co-Authors: A.l.n. ReddyAbstract:This paper presents MVSS, a storage System for active storage devices MVSS offers a single framework for supporting various services at the device level. It provides a flexible interface for associating services to a file through multiple views of the file Similar to views of a database in a multiview database System, views in MVSS are generated dynamically and are not stored on physical storage devices. MVSS represents each view of an underlying file through a separate entry in the file System Namespace. MVSS separates the deployment of services from file System implementations and, thus, allows services to be migrated to storage devices. The paper presents the design of MVSS and how different services can be supported in MVSS at the device level. To illustrate our approach, we implemented a prototype System on PCs running Linux. We present results from example applications implemented on the prototype and discuss a variety of architectural issues including mixed workloads.
-
ICDCS - MVSS: Multi-View Storage System
Proceedings 21st International Conference on Distributed Computing Systems, 1Co-Authors: A.l.n. ReddyAbstract:Presents MVSS, a storage System for active storage devices. MVSS offers a single framework for supporting various services at the device level. It provides a flexible interface for associating services to a file through multiple views of the file. Similar to views of a database in a multi-view database System, views in MVSS are generated dynamically and are not stored on physical storage devices. MVSS represents each view of an underlying file through a separate entry in the file System Namespace. MVSS separates the deployment of services from file System implementations and thus allows services to be migrated to the storage devices. The paper presents the design of MVSS and shows how different services can be supported in MVSS at the device level. To illustrate our approach, we implemented a prototype System on PCs running Linux. We present results from the prototype implementation to demonstrate the effectiveness of our approach.
Parag Gokhale - One of the best experts on this subject based on the ideXlab platform.
-
data object store and server for a cloud storage environment including data deduplication and data management across multiple cloud storage sites
2010Co-Authors: Anand Prahlad, Marcus S Muller, Rajiv Kottomtharayil, Srinivas Kavuri, Parag Gokhale, Manoj Kumar VijayanAbstract:Data storage operations, including content-indexing, containerized deduplication, and policy-driven storage, are performed within a cloud environment. The Systems support a variety of clients and cloud storage sites that may connect to the System in a cloud environment that requires data transfer over wide area networks, such as the Internet, which may have appreciable latency and/or packet loss, using various network protocols, including HTTP and FTP. Methods are disclosed for content indexing data stored within a cloud environment to facilitate later searching, including collaborative searching. Methods are also disclosed for performing containerized deduplication to reduce the strain on a System Namespace, effectuate cost savings, etc. Methods are disclosed for identifying suitable storage locations, including suitable cloud storage sites, for data files subject to a storage policy. Further, Systems and methods for providing a cloud gateway and a scalable data object store within a cloud environment are disclosed, along with other features.
-
performing data storage operations with a cloud storage environment including automatically selecting among multiple cloud storage sites
2010Co-Authors: Anand Prahlad, Marcus S Muller, Rajiv Kottomtharayil, Srinivas Kavuri, Parag GokhaleAbstract:Systems and methods are disclosed for performing data storage operations, including content-indexing, containerized deduplication, and policy-driven storage, within a cloud environment. The Systems support a variety of clients and cloud storage sites that may connect to the System in a cloud environment that requires data transfer over wide area networks, such as the Internet, which may have appreciable latency and/or packet loss, using various network protocols, including HTTP and FTP. Methods are disclosed for content indexing data stored within a cloud environment to facilitate later searching, including collaborative searching. Methods are also disclosed for performing containerized deduplication to reduce the strain on a System Namespace, effectuate cost savings, etc. Methods are disclosed for identifying suitable storage locations, including suitable cloud storage sites, for data files subject to a storage policy. Further, Systems and methods for providing a cloud gateway and a scalable data object store within a cloud environment are disclosed, along with other features.
