Repository logo
Log in(current)
Repository logoMIT Open ScholarshipDSpace@MIT
  1. Home
  2. MIT Open Access Articles
  3. MIT Open Access Articles
  4. How to tell if your cloud files are vulnerable to drive crashes

How to tell if your cloud files are vulnerable to drive crashes

Thumbnail Image
Download
Name

Rivest_How to tell.pdf

Size

1007.18 KB

Format

Adobe PDF

Checksum (MD5)

84f67c912e6af0ca915c3e878d9ddaea

Author(s)
Bowers, Kevin D.
•
van Dijk, Marten
•
Juels, Ari
•
Oprea, Alina
•
Rivest, Ronald L.
Date Issued
October 2011
Journal
Proceedings of the 18th ACM conference on Computer and Communications Security, CCS '11
Publisher
Association for Computing Machinery
Citation
Bowers, Kevin D. et al. “How to Tell If Your Cloud Files Are Vulnerable to Drive Crashes.” Proceedings of the 18th ACM conference on Computer and Communications Security, CCS'11, October 17–21, 2011, Chicago, Illinois, USA. pp.501-514. ACM Press, 2011.Web.
Version
Author's final manuscript
Abstract
This paper presents a new challenge--verifying that a remote server is storing a file in a fault-tolerant manner, i.e., such that it can survive hard-drive failures. We describe an approach called the Remote Assessment of Fault Tolerance (RAFT). The key technique in a RAFT is to measure the time taken for a server to respond to a read request for a collection of file blocks. The larger the number of hard drives across which a file is distributed, the faster the read-request response. Erasure codes also play an important role in our solution. We describe a theoretical framework for RAFTs and offer experimental evidence that RAFTs can work in practice in several settings of interest.
MIT Department
Massachusetts Institute of Technology. Computer Science and Artificial Intelligence Laboratory
Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science
Terms of Use
Creative Commons Attribution-Noncommercial-Share Alike 3.0
http://creativecommons.org/licenses/by-nc-sa/3.0/
Persistent DSpace Link
http://hdl.handle.net/1721.1/72402
DOI of Published Version
https://doi.org/10.1145/2046707.2046766
Repository logo
PrivacyPermissionsAccessibilityContact us
Repository logo
Notify us about copyright concerns.