Representative, Reproducible, and Practical Benchmarking of File and Storage Systems

Total Page:16

File Type:pdf, Size:1020Kb

Representative, Reproducible, and Practical Benchmarking of File and Storage Systems REPRESENTATIVE, REPRODUCIBLE, AND PRACTICAL BENCHMARKING OF FILE AND STORAGE SYSTEMS by Nitin Agrawal A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy (Computer Sciences) at the UNIVERSITY OF WISCONSIN–MADISON 2009 i To my parents ii ACKNOWLEDGMENTS First and foremost I would like to thank my advisors, Andrea and Remzi; I couldn’t have asked for better. During our weekly meetings, more often than not, I went in with a laundry list of frenzied thoughts and messy graphs, and came out with a refined idea. Graciously, they made me feel as if I was the one responsible for this outcome; I wish I had been better prepared to get more out of our meetings. Remzi showed me how someone could do serious research without taking oneself too seriously, though it will be a lasting challenge for me to come anywhere close to how effortlessly he does it. As an advisor, he genuinely cares for his student’s well being. On many occasions my spirits got refreshed after getting an “are you OK?” email from him. Remzi not only provided a constant source of good advice ranging from conference talk tips to tennis racquet selection, but his ability to find “altitude” in my work when none existed transformed a series of naive ideas into a dissertation. Most students would consider themselves lucky to have found one good advisor, I was privileged to have two. Andrea constantly raised the bar and challenged me to do better; the thesis is all the more thorough due to her persistence. I was always amazed how she could understand in a few minutes the implications of my work far beyond my own under- standing. Andrea’s meticulous advising was the driving force behind the completion and acceptance of much of my work. I would like to thank my thesis committee members Mike Swift, Karu Sankaralingam and Mark Craven, for their useful suggestions and questions about my research during my defense talk. I would especially like to thank Mike for his advice and interest in my work iii throughout, and for giving me an opportunity to teach his undergraduate operating systems class. During my six years in Wisconsin, I have had a wonderful set of colleagues Leo Arulraj, Lakshmi Bairavasundaram, John Bent, Nate Burnett, Tim Denehy, Haryadi Gunawi, Todd Jones, Shweta Krishnan, Andrew Krioukov, Joe Meehan, Florentina Popovici, Vijayan Prabhakaran, Abhishek Rajimwale, Meenali Rungta, Muthian Sivathanu, Sriram Subra- manian, Swami Sundararaman, and Yupu Zhang; being the last of Remzi and Andrea’s pre-tenure hires, I perhaps overlapped with a larger than usual group of students to my benefit. I will especially miss our late night chats in the hallway and lunch outings to the food carts. Muthian and Ina kindled my interest in the group and provided a patient ear to a curious (and clueless) first year graduate student, I thank them for that. I also thank Leo for taking over some of the work on Compressions while I was busy writing my dissertation. My officemates John, Todd, Shweta, and Swami have all been awesome (even taking care of my plants during my absence!). I have greatly benefited from my internships at Microsoft Research (Redmond and Sil- icon Valley) and IBM Almaden; my internship work at MSR Redmond in fact became the basis for my thesis itself. I thank my mentors and colleagues Bill Bolosky, John Douceur, Jay Lorch at MSR Redmond, Ted Wobber at MSR Silicon Valley, and Ying Chen at IBM Almaden. I am grateful to John and Ted in particular for providing a terrific internship experience as mentors. Gautham and Lakshmi, my roommates for five years, made my stay in Madison a most pleasant one. Their friendship and camaraderie provided comfort during times when I felt low, and a reason to celebrate even minor accomplishments. I will miss my discussions with Gau on all things not related to work. Lakshmi had the added burden of being both a friend and a colleague. He mentored my research in more ways than he cares to remember. I thank Anoop for being part of our Madison family during the first two years. Having iv Akash as roommate for the last year during a tough job market somehow made the process less stressful. My stay in Madison wouldn’t have been the same without the company of wonderful friends Ankit, Cindy, Jayashree, Neelam, Raman, Shweta and Swami to name a few. I con- stantly ignored Shweta and Neelam’s concern about my health and eating habits, but they continued to provide food and friendship during their years here. Evening coffee breaks with them became a daily stress buster, and our escapades during a summer internship in California will always be memorable. Cindy not only provided constant company in the department, but also pleasant musical interludes. Having Ankit live right next door made his apartment my “third place”; movie and dinner nights eventually gave way to more en- tertaining ones playing Wii. Mayur, and later on Priyank, played host to numerous east coast trips; knowing that they will be close to Princeton is a comforting thought. Deborshi and Siddhartha have been good friends throughout these years. The company of my cousins in the US, Arvind, Ashish, Saurabh and Shubha, provided me a feeling of home away from home. My sister Neha has always been the kind of loving sister who is more happy for my accomplishments than I myself. Talking to her on phone has been my refuge from the monotony of work and I have come to cherish the time that we get to spend together. Finally, I would like to thank my parents for their unconditional love and support; this Ph.D. would not have been possible without them. They have always helped me see the good in everything and shaped my perspective for the better. Whenever I doubted my abilities, their encouragement put me right back on track. The pride in their eyes on seeing me graduate made it all seem worthwhile. v TABLE OF CONTENTS Page LIST OF TABLES ................................... ix LIST OF FIGURES .................................. x ABSTRACT ......................................xiv 1 Introduction .................................... 1 1.1 Representative and Reproducible File-System BenchmarkingState . 3 1.1.1 CharacteristicsofFile-SystemMetadata . ..... 4 1.1.2 GeneratingFile-SystemBenchmarkingState . .... 6 1.2 Practical Benchmarking for Large, Real Workloads . ........ 8 1.3 Representative, Reproducible and Practical Benchmark Workloads . 11 1.4 Overview ................................... 13 2 Five Year Study of File System Metadata .................... 15 2.1 Methodology ................................. 18 2.1.1 Datacollection ............................ 18 2.1.2 Dataproperties ............................ 19 2.1.3 Datapresentation.. .. .. .. .. .. .. .. 20 2.1.4 Limitations .............................. 22 2.2 Files...................................... 22 2.2.1 Filecountperfilesystem. 22 2.2.2 Filesize................................ 23 2.2.3 Fileage................................ 28 2.2.4 File-nameextensions . 29 2.2.5 Unwrittenfiles ............................ 32 2.3 Directories................................... 34 2.3.1 Directorycountperfilesystem. 34 2.3.2 Directorysize............................. 35 2.3.3 Specialdirectories . 38 2.3.4 Namespacetreedepth . 39 vi Page 2.3.5 Namespacedepthmodel . 45 2.4 SpaceUsage.................................. 47 2.4.1 Capacityandusage. .. .. .. .. .. .. .. 47 2.4.2 Changesinusage........................... 49 2.5 RelatedWork ................................. 52 2.6 Discussion................................... 54 2.7 Conclusion .................................. 56 3 Generating Realistic Impressions for File-System Benchmarking ....... 57 3.1 ExtendedMotivation ............................. 61 3.1.1 DoesFile-SystemStructureMatter? . .. 61 3.1.2 GoalsforGeneratingFSImages . 63 3.1.3 ExistingApproaches . 64 3.2 TheImpressionsFramework . 65 3.2.1 ModesofOperation . .. .. .. .. .. .. .. 65 3.2.2 BasicTechniques.. .. .. .. .. .. .. .. 67 3.2.3 CreatingValidMetadata . 68 3.2.4 ResolvingArbitraryConstraints . .. 74 3.2.5 InterpolationandExtrapolation . .. 80 3.2.6 FileContent.............................. 84 3.2.7 DiskLayoutandFragmentation . 85 3.2.8 Performance ............................. 86 3.3 CaseStudy:DesktopSearch . 87 3.3.1 RepresentativeImages . 87 3.3.2 ReproducibleImages . 91 3.4 OtherApplications .............................. 94 3.4.1 GeneratingRealisticRulesofThumb . 94 3.4.2 TestingHypothesis . 94 3.5 RelatedWork ................................. 96 3.5.1 ToolsforGeneratingFile-SystemImages . ... 96 3.5.2 Tools and Techniques for Improving Benchmarking . ..... 97 3.5.3 ModelsforFile-SystemMetadata . 98 3.6 Conclusion .................................. 98 vii Page 4 Practical Storage System Benchmarking with Compressions .........100 4.1 Background ..................................103 4.1.1 StorageStack.............................104 4.1.2 StorageSystems .. .. .. .. .. .. .. ..105 4.2 TheCompressionsFramework . 107 4.2.1 DesignGoals .............................107 4.2.2 BasicArchitecture . .108 4.2.3 BlockClassificationandDataSquashing . 110 4.2.4 MetadataRemapping. .115 4.2.5 SyntheticContentGeneration . 116 4.3 TheStorageModel ..............................119 4.3.1 ModelExpectationsandGoals . .119 4.3.2 TheDeviceModel . .. .. .. .. .. .. ..120 4.3.3 StorageStackModel . .124 4.4 Evaluation...................................126 4.4.1 ExperimentalPlatform . .127 4.4.2 PerformanceEvaluation . .127 4.4.3 FidelityEvaluation . .130 4.5 RelatedWork .................................138 4.5.1 StorageSystemModelingandEmulation
Recommended publications
  • 855400Cd46b6c9e7683b5ace58a55234.Pdf
    Ars TeAchrsn iTceachnica UK Register Log in ▼ ▼ Ars Technica has arrived in Europe. Check it out! × Encryption options are great, but Apple's attitude on checksums is still funky. by Adam H. Leventhal - Jun 26, 2016 1:00pm UTC KEEPING ON TRUCKING INDEPENDENCE, WHAT INDEPENDENCE? Two hours or so of WWDC keynoting and Tim Cook didn't mention a new file system once? Andrew Cunningham This article was originally published on Adam Leventhal's blog in multiple parts. Programmer Andrew Nõmm: "I had to be made Apple announced a new file system that will make its way into all of its OS variants (macOS, tvOS, iOS, an example of as a warning to all IT people." watchOS) in the coming years. Media coverage to this point has been mostly breathless elongations of Apple's developer documentation. With a dearth of detail I decided to attend the presentation and Q&A with the APFS team at WWDC. Dominic Giampaolo and Eric Tamura, two members of the APFS team, gave an overview to a packed room; along with other members of the team, they patiently answered questions later in the day. With those data points and some first-hand usage I wanted to provide an overview and analysis both as a user of Apple-ecosystem products and as a long-time operating system and file system developer. The overview is divided into several sections. I'd encourage you to jump around to topics of interest or skip right to the conclusion (or to the tweet summary). Highest praise goes to encryption; ire to data integrity.
    [Show full text]
  • Toward Automatic Context-Based Attribute Assignment for Semantic file Systems
    Toward automatic context-based attribute assignment for semantic file systems Craig A. N. Soules, Gregory R. Ganger CMU-PDL-04-105 June 2004 Parallel Data Laboratory Carnegie Mellon University Pittsburgh, PA 15213-3890 Abstract Semantic file systems enable users to search for files based on attributes rather than just pre-assigned names. This paper devel- ops and evaluates several new approaches to automatically generating file attributes based on context, complementing existing approaches based on content analysis. Context captures broader system state that can be used to provide new attributes for files, and to propagate attributes among related files; context is also how humans often remember previous items [2], and so should fit the primary role of semantic file systems well. Based on our study of ten systems over four months, the addition of context-based mechanisms, on average, reduces the number of files with zero attributes by 73%. This increases the total number of classifiable files by over 25% in most cases, as is shown in Figure 1. Also, on average, 71% of the content-analyzable files also gain additional valuable attributes. Acknowledgements: We thank the members and companies of the PDL Consortium (including EMC, Hewlett-Packard, HGST, Hitachi, IBM, Intel, LSI Logic, Microsoft, Network Appliance, Panasas, Seagate, Sun, and Veritas) for their interest, insights, feedback, and support. We thank IBM and Intel for hardware grants supporting our research efforts. Keywords: semantic filesystems, context, attributes, classfication 1 Introduction As storage capacity continues to increase, the number of files belonging to an individual user has increased accordingly. Already, storage capacity has reached the point where there is little reason for a user to delete old content—in fact, the time required to do so would be wasted.
    [Show full text]
  • Dominic Giampaolo Interview Page 1 of 4
    frontwheeldrive.com: dominic giampaolo interview Page 1 of 4 home | interviews | reviews | mentors | about | contact Anno Dominic Dominic Giampaolo [by Tom Georgoulias] Dominic Giampaolo isn't exactly a household name, but chances are high you've actually seen the benefits of his work. Dominic was the guy who tracked down a bug in the graphics driver during his days at SGI that was inhibiting a digital effects studio from getting their work completed on the movie Speed. He was also responsible for tracking down a gnarly bug in an eight processor system that only occured within a window of 12 nanoseconds. Dominic worked on various portions of the RealityEngine before Google moving to Be Inc. as a kernel engineer and file system architect for the BeOS. Easily the best search I met Dominic several years ago through a mutual friend and we've been engine out there. corresponding ever since, discussing topics like music, traveling, and software on a weekly basis. Dominic recently left Be Inc. for a senior project management position at Google, so I felt it was time to put him under the BeDope Interview frontwheeldrive spotlight and get his take on various events such as the rise of TA short but entertaining Linux and the Microsoft anti-trust trial. interview from BeDope, the Be Inc. fan site that makes up it's own news. frontwheeldrive: As I understand it, after your graduation you basically drove from Worcester, MA to San Jose, CA and landed a job at SGI. How did you like it there? Inside the BeOS Take a stroll through the BeOS with Dominic and Dominic Giampaolo: I loved working at SGI.
    [Show full text]
  • A Bibliography of Books and Articles About UNIX and UNIX Programming
    A Bibliography of Books and Articles about UNIX and UNIX Programming Nelson H. F. Beebe University of Utah Department of Mathematics, 110 LCB 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Tel: +1 801 581 5254 FAX: +1 801 581 4148 E-mail: [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe/ 02 July 2021 Version 4.44 Abstract General UNIX texts [AL92a, AL95a, AL95b, AA86, AS93b, Ari92, Bou90a, Chr83a, Chr88, CR94, Cof90, Coh94, Dun91a, Gar91, Gt92a, Gt92b, This bibliography records books and historical Hah93, Hah94a, HA90, Hol92, KL94, LY93, publications about the UNIX operating sys- LR89a, LL83a, MM83a, Mik89, MBL89, tem, and UNIX programming tools. It mostly NS92, NH91, POLo93, PM87, RRF90, excludes networks and network programming, RRF93, RRH94, Rus91, Sob89, Sob91, which are treated in a separate bibliography, Sob95, Sou92, TY82b, Tim93, Top90a, internet.bib. This bibliography was started Top90b, Val92b, SSC93, WMP92] from material in postings to the sunflash list, volume 46, number 17, October 1992, and volume 57, number 29, September 1993, by Samuel Ko (e-mail: [email protected]), and then significantly extended by the present Catalogs and book lists author. Entry commentaries are largely due to S. Ko. [O'R93, Spu92, Wri93] 1 2 Communications software History [Cam87, dC87, dG93, Gia90] [?, ?, Cat91, RT74, RT79a] Compilers Linux [DS88, JL78, Joh79, JL87a, LS79, LMB92, [BBD+96, BF97, HP+95, Kir95a, Kir95b, MB90, SF85] PR96b, Sob97, SU94b, SU95, SUM95, TGB95, TG96, VRJ95,
    [Show full text]
  • OPINION SYSTEMS WEB SYSADMIN HARDWARE COLUMNS BOOK REVIEWS Book Reviews CONFERENCES
    J U N E 2 0 1 0 V O L U M E 3 5 N U M B E R 3 OPINION Musings 2 Rik Farrow SyStemS MINIX 3: Status Report and Current Research 7 andRew Tanenbaum, Raja appuswa my, HeRbert bos, LoRenzo Cavall aRo, THE USENIX MAGAZINE CRisTiano Giuffrida , T o m ásˇ H R u by´ , jorriT HeRdeR, Erik van deR kouwe, and david van mooLenbRoek Web 3D Web Contenders 14 jim sanGwine SySadmin Programming with Technological Ritual and Alchemy 22 Alva L . Couch Building a Virtual DNS Appliance Using Solaris 10, BIND, and VMware 27 andRew seeLy LISA: Beginning the Journey 35 m att simmons HardWare Small Embedded Systems 38 Rudi van Drunen COlumns Practical Perl Tools: Making Stuff Up 48 david n. Bl ank-edeL m an Pete’s All Things Sun: Exadata V2 Architecture and Why It Matters 54 peTeR baeR GaLvin iVoyeur: Pockets-o-Packets, Part 1 59 dave josepHsen /dev/random: Five Common Misconceptions About information Security 63 Robert G. Ferrell book revIews Book Reviews 65 Br andon CHinG and sa m StoveR uSenix NOTES Notice of Annual Meeting 67 Results of the Election for the USENIX Board of Directors, 2010–2012 67 Writing for ;login: 68 ConferenceS FAST ’10: 8th USENIX Conference on File and Storage ­Technologies 69 First USENIX Workshop on Sustainable Information Technology (SustainIT ’10) 89 2nd USENIX Workshop on the Theory and Practice of Provenance (TaPP ’10) 96 The Advanced Computing Systems Association june10covers.indd 1 5.10.10 10:26 AM Upcoming Events 19th USENIX SEcUrIty Symposium 9th USENIX Symposium oN opErating SyStEmS (USENIX SEcUrIty ’10) desigN aNd ImplEmentatIoN
    [Show full text]
  • Practical File System Design:The Be File System, Dominic Giampaolo Half Title Page Page I
    Practical File System Design:The Be File System, Dominic Giampaolo half title page page i Practical File System Design with the Be File System Practical File System Design:The Be File System, Dominic Giampaolo BLANK page ii Practical File System Design:The Be File System, Dominic Giampaolo title page page iii Practical File System Design with the Be File System Dominic Giampaolo Be, Inc. ® MORGAN KAUFMANN PUBLISHERS, INC. San Francisco, California Practical File System Design:The Be File System, Dominic Giampaolo copyright page page iv Editor Tim Cox Director of Production and Manufacturing Yonie Overton Assistant Production Manager Julie Pabst Editorial Assistant Sarah Luger Cover Design Ross Carron Design Cover Image William Thompson/Photonica Copyeditor Ken DellaPenta Proofreader Jennifer McClain Text Design Side by Side Studios Illustration Cherie Plumlee Composition Ed Sznyter, Babel Press Indexer Ty Koontz Printer Edwards Brothers Designations used by companies to distinguish their products are often claimed as trademarks or registered trademarks. In all instances where Morgan Kaufmann Publishers, Inc. is aware of a claim, the product names appear in initial capital or all capital letters. Readers, however, should contact the appropriate companies for more complete information regarding trademarks and registration. Morgan Kaufmann Publishers, Inc. Editorial and Sales Office 340 Pine Street, Sixth Floor San Francisco, CA 94104-3205 USA Telephone 415/392-2665 Facsimile 415/982-2665 Email [email protected] WWW http://www.mkp.com Order toll free 800/745-7323 c 1999 Morgan Kaufmann Publishers, Inc. All rights reserved Printed in the United States of America 03 02 01 00 99 5 4 3 2 1 No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means—electronic, mechanical, photocopying, recording, or otherwise—without the prior written permission of the publisher.
    [Show full text]
  • Practical File System Design Online
    lgxdb (Download ebook) Practical File System Design Online [lgxdb.ebook] Practical File System Design Pdf Free Dominic Giampaolo audiobook | *ebooks | Download PDF | ePub | DOC Download Now Free Download Here Download eBook #1671728 in eBooks 2013-08-29 2013-08-29File Name: B008I3ARBI | File size: 29.Mb Dominic Giampaolo : Practical File System Design before purchasing it in order to gage whether or not it would be worth my time, and all praised Practical File System Design: 2 of 3 people found the following review helpful. Decent survey of ideas, needs more breadth, depth, clarityBy A CustomerAs other reviewers have pointed out, the author starts off by apologetically lamenting that he didn't have much time to go into very detailed analysis on other file systems. The author seems very knowledgeable in general, and it's a shame he didn't have more time to add some more breadth to the book. Some of my all-time favorite books are Patterson and Hennessey's two computer architecture books, because they are very dense with a wide range of well- explained ideas. This book is much less dense.Perhaps the most annoying thing about this book though is that he doesn't finish his thoughts. I felt that often, just as he was getting to the interesting part after cutting through the fluffy descriptions of his design choices, he would leave the topic and not come back. The must frustrating part of this was that after skipping over many pertinent details of how he actually built the BeFS, he spends an excruciating amount of time describing the vnode layer and the exact API that the file system driver must write too -- something I feel would have been better left to a Be-specific API programming manual.The editing could have used some help.
    [Show full text]
  • Decoding the APFS File System Digital Investigation
    Digital Investigation xxx (2017) 1e26 Contents lists available at ScienceDirect Digital Investigation journal homepage: www.elsevier.com/locate/diin Decoding the APFS file system * Kurt H. Hansen , Fergus Toolan Norwegian Police University College, PO Box 5027, Majorstuen, 0301 Oslo, Norway article info abstract Article history: File systems have always played a vital role in digital forensics and during the past 30e40 years many of Received 22 April 2017 these have been developed to suit different needs. Some file systems are more tightly connected to a Received in revised form specific Operating System (OS). For instance HFS and HFSþ have been the file systems of choice in Apple 21 June 2017 devices for over 30 years. Accepted 18 July 2017 Much has happened in the evolution of storage technologies, the capacity and speed of devices has Available online xxx increased and Solid State Drives (SSD) are replacing traditional drives. All of these present challenges for file systems. APFS is a file system developed from first principles and will, in 2017, become the new file Keywords: APFS system for Apple devices. File systems To date there is no available technical information about APFS and this is the motivation for this article. macOS © 2017 Elsevier Ltd. All rights reserved. File recovery Introduction APFS artefacts and a means to interpret them manually. Finally, we conclude in Section Conclusions. Apple has used the HFS/HFSþ file systems for the past 30 years. Many abbreviations are used in this article. A list of these can be The HFS (Hierarchical File System) was introduced in 1985 and had found in Appendix C, Table C.20.
    [Show full text]
  • Recovery Techniques to Improve File System Reliability
    RECOVERY TECHNIQUES TO IMPROVE FILE SYSTEM RELIABILITY by Swaminathan Sundararaman B.E. (Hons.) Computer Science (Birla Institute of Technology and Science (Pilani), India) 2005 M.S. Computer Sciences (Stony Brook University) 2007 A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Sciences University of Wisconsin-Madison 2011 Committee in charge: Prof. Andrea C. Arpaci-Dusseau (Co-chair) Prof. Remzi H. Arpaci-Dusseau (Co-chair) Prof. Ben Liblit Prof. Michael M. Swift Prof. Shan Lu Prof. Jon Eckhardt ii iv v To my parents vi vii Acknowledgements I would like to express my heart-felt thanks to my advisors, Andrea Arpaci-Dusseau and Remzi Arpaci-Dusseau, who guided me in this endeavor and taught me how to do research. I always wanted to build really cool systems during my Ph.D. Not only did they let me do this, but they also taught me the valuable lesson that solutions (or systems) are just a small part of doing research. I also learnt the importance of clarity in both writing and presentation from them. I would like to thank Andrea for teaching me the values of patience, good ques- tions, and paying attention to details. I would like to thank Remzi for helping me select interesting projects and, most importantly, for showing me that research is a lot of fun. I am ever grateful to Remzi for taking the time to write me a long email and talk with me on the phone while I was deciding between universities. If not for that email, I would have ended up taking a full-time position at one of the companies in the Bay Area – and regretted not doing a Ph.D.
    [Show full text]
  • The Global Intelligent File System Framework
    _________________________________________________________________________Swansea University E-Theses The global intelligent file system framework. Gooch, Joanna How to cite: _________________________________________________________________________ Gooch, Joanna (2006) The global intelligent file system framework.. thesis, Swansea University. http://cronfa.swan.ac.uk/Record/cronfa42337 Use policy: _________________________________________________________________________ This item is brought to you by Swansea University. Any person downloading material is agreeing to abide by the terms of the repository licence: copies of full text items may be used or reproduced in any format or medium, without prior permission for personal research or study, educational or non-commercial purposes only. The copyright for any work remains with the original author unless otherwise specified. The full-text must not be sold in any format or medium without the formal permission of the copyright holder. Permission for multiple reproductions should be obtained from the original author. Authors are personally responsible for adhering to copyright and publisher restrictions when uploading content to the repository. Please link to the metadata record in the Swansea University repository, Cronfa (link given in the citation reference above.) http://www.swansea.ac.uk/library/researchsupport/ris-support/ The Global Intelligent File System Framework Joanna Gooch BSc. (Wales) A thesis submitted to the University of Wales in candidature for the degree of Philosophiae Doctor Department of Computer Science University of Wales, Swansea September 2006 ProQuest Number: 10798045 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a com plete manuscript and there are missing pages, these will be noted.
    [Show full text]
  • Research Proposal (PDF)
    Research Proposal Revision: 1.10 Stewart Smith [email protected] Contents 1 Introduction 2 1.1 Walnut.......................................... ..... 2 1.2 WalnutStorage................................... ....... 2 1.3 WalnutPersistenceandconsistency. .............. 2 1.4 ObjectRevisionsandVersioning . ............ 2 1.5 Aims............................................ .... 3 2 Research Context 3 2.1 ConsistencyinPersistentSystems . ............. 3 2.2 ComparisonwithUNIXSemantics . .......... 3 2.3 FilesystemMetadataConsistency . ............. 3 2.4 Revisiontracking................................ ......... 4 3 Research Plan and Methods 4 3.1 ResearchMethods ................................. ....... 4 3.2 ProposedThesisChapterHeadings . ............ 4 3.3 Timetable....................................... ...... 5 3.4 FacilitiesNeeded ................................ ......... 5 3.4.1 Testbed ....................................... ... 5 3.4.2 DevelopmentMachine . ...... 5 4 Relevance of the Proposal 5 1 Stewart Smith(13082647) Research Proposal [email protected] Abstract ”Walnut Kernel”: To design and implement a data object storage system with advanced features such as user visible transactions and support for object versioning. 1 Introduction 1.1 Walnut Walnut[4] is a persistent password capability based operating system extending many of the ideas first presented in the Password Capability System[17]. Being a persistent system, all state information is saved on shutdown and when you restart the system, it should bring you back to exactly the way it was before shutdown. During recent work on the Walnut Kernel, it has become apparent that areas of the data storage system would be inadequate for use in a production system where data consistency and reliability are priorities. 1.2 Walnut Storage Processes running on Walnut access blocks of data (objects) referenced by a unique object ID. These objects are then mapped into the address space of the process. Conceptually, this is similar to the UNIX mmap function.
    [Show full text]
  • Abstract—This Paper Lays out Different Issues and Solutions in the Design
    IJCSI International Journal of Computer Science Issues, Vol. 8, Issue 1, January 2011 ISSN (Online): 1694-0814 www.IJCSI.org 295 A Method for Designing an Operating System for Plug and Play Bootstrap Loader USB Drive Dr. T. Jebarajan 1, K. Siva Sankar 2 1 Principal, V.V Engg College Tamil Nadu, India. 2 Lecturer, Noorul Islam University. Tamil Nadu, India. Abstract Nasm is required. It requires a target machine for the This paper lays out different issues and solutions in the design of operating system. It supports a range of object file formats, an operating system with an inbuilt kernel memory for data including Linux and *BSD a.out, ELF, COFF, Mach-O, storage and USB (Universal Serial Bus) drive with bootstrap Microsoft 16-bit OBJ, Win32 and Win64. It will also loader. This relates from the minimum features required for a output plain binary files. Its syntax is designed to be simple program to become the kernel and how this kernel should be and easy to understand, similar to Intel's but less complex written into the boot sector of a hard disk drive depend upon the machine architecture, so that it gets loaded into the computer for fast accessing. The design and bootstrap strategy will memory automatically and it restores the disk drive in to its vary with the underlying machine architecture. For this original state. It highlights how this operating system can be design, consider the target machine as an Intel x86 based made to support user specific authentication, keyboard, hardware with minimum 1MB RAM, USB disk drive, networking, peripherals, file system access etc.
    [Show full text]