DOCSLIB.ORG

File Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
File Systems ;login JUNE 2013 VOL. 38, NO. 3 : File Systems & Linux File System Evolution via Patch Analysis Lanyue Lu, Andrea C. Arpaci-Dusseau, Remzi H. Arpaci-Dusseau, and Shan Lu &Interview with Ted Ts’o Rik Farrow & Ganeti: Cluster Virtualization Manager Guido Trotter and Tom Limoncelli & Future Interfaces for Non- Volatile Memory Andy Rudoff Columns Practical Perl Tools: Constants David Blank-Edelman IPython and Notebook David Beazley Sampling and Monitoring Dave Josephsen For Good Measure: Calculating Risk Dan Geer and Dan Conway /dev/random: Clusters and Understanding *nix File Permissions Robert Ferrell Book Reviews Mark Lamourine and Trey Darley Conference Reports FAST ’13: 11th USENIX Conference on File and Storage Technologies UPCOMING EVENTS FOR A COMPLETE LIST OF USENIX AND USENIX CO-SPONSORED EVENTS, SEE WWW.USENIX.ORG/CONFERENCES 2013 USENIX Federated Conferences Week Workshops Co-located with USENIX Security ’13 June 24–28, 2013, San Jose, CA, USA www.usenix.org/conference/fcw13 EVT/WOTE ’13: 2013 Electronic Voting Technology Workshop/Workshop on Trustworthy Elections USENIX ATC ’13: 2013 USENIX Annual Technical August 12–13, 2013 Conference www.usenix.org/conference/evtwote13 June 26–28, 2013 USENIX Journal of Election Technology www.usenix.org/conference/atc13 and Systems (JETS) Published in conjunction with EVT/WOTE ICAC ’13: 10th International Conference on www.usenix.org/jets Autonomic Computing Submissions for Volume 1, Issue 2, due: August 6, 2013 June 26–28, 2013 www.usenix.org/conference/icac13 CSET ’13: 6th Workshop on Cyber Security Experimentation and Test HotPar ’13: 5th USENIX Workshop on Hot Topics in August 12, 2013 Parallelism www.usenix.org/conference/cset13 June 24–25, 2013 www.usenix.org/conference/hotpar13 HealthTech ’13: 2013 USENIX Workshop on Health Information Technologies UCMS ’13: 2013 USENIX Configuration Safety, Security, Privacy, and Interoperability of Health Management Summit Information Technologies June 24, 2013 August 12, 2013 www.usenix.org/conference/ucms13 www.usenix.org/conference/healthtech13 8th International Workshop on Feedback Computing LEET ’13: 6th USENIX Workshop on Large-Scale June 25, 2013 Exploits and Emergent Threats www.usenix.org/conference/feedbackcomputing13 August 12, 2013 www.usenix.org/conference/leet13 ESOS ’13: 2013 Workshop on Embedded Self-Organizing Systems FOCI ’13: 3rd USENIX Workshop on Free and Open June 25, 2013 Communications on the Internet www.usenix.org/conference/esos13 August 13, 2013 www.usenix.org/conference/foci13 HotCloud ’13: 5th USENIX Workshop on Hot Topics in Cloud Computing HotSec ’13: 2013 USENIX Summit on Hot Topics June 25–26, 2013 in Security www.usenix.org/conference/hotcloud13 August 13, 2013 www.usenix.org/conference/hotsec13 WiAC ’13: 2013 USENIX Women in Advanced Computing Summit WOOT ’13: 7th USENIX Workshop on June 26–27, 2013 Offensive Technologies www.usenix.org/conference/wiac13 August 13, 2013 www.usenix.org/conference/woot13 HotStorage ’13: 5th USENIX Workshop on Hot Topics in Storage and File Systems LISA ’13: 27th Large Installation System June 27–28, 2013 Administration Conference www.usenix.org/conference/hotstorage13 November 3–8, 2013, Washington, D.C., USA www.usenix.org/conference/lisa13 HotSWUp ’13: 5th Workshop on Hot Topics in Software Upgrades SESA ’13: 2013 USENIX Summit for Educators in June 28, 2013 System Administration www.usenix.org/conference/hotswup13 CO-LOCATED WITH LISA ’13 USENIX Security ’13: 22nd USENIX Security November 5, 2013, Washington, D.C., USA www.usenix.org/conference/sesa13 Symposium Submissions due: July 30, 2013 August 14–16, 2013, Washington, D.C., USA www.usenix.org/conference/usenixsecurity13 FAST ’14: 12th USENIX Conference on File and Storage Technologies February 17–20, 2014, Santa Clara, CA, USA www.usenix.org/conference/fast14 Submissions due: September 26, 2013 JUNE 2013 VOL. 38, NO. 3 EDITOR Rik Farrow [email protected] EDITORIAL MANAGING EDITOR Rikki Endsley 2 Musings Rik Farrow [email protected] COPY EDITOR OPINION Steve Gilmartin 6 On Teaching Style and Maintainability Geoff Kuenning [email protected] PRODUCTION Arnold Gatilao FILE SYSTEMS Casey Henderson 10 A Study of Linux File System Evolution Michele Nelson Lanyue Lu, Andrea C. Arpaci-Dusseau, Remzi H. Arpaci-Dusseau, TYPESETTER and Shan Lu Star Type [email protected] 18 Ted Ts’o on Linux File Systems: An Interview USENIX ASSOCIATION Rik Farrow 2560 Ninth Street, Suite 215, Berkeley, California 94710 22 Shingled Magnetic Recording: Areal Density Increase Requires New Phone: (510) 528-8649 Data Management FAX: (510) 548-5738 Tim Feldman and Garth Gibson www.usenix.org ;login: is the official magazine of the USENIX CLUSTERS Association. ;login: (ISSN 1044-6397) 31 Ganeti: Cluster Virtualization Manager is published bi-monthly by the USENIX Guido Trotter and Tom Limoncelli Association, 2560 Ninth Street, Suite 215, Berkeley, CA 94710. 37 PRObE: A Thousand-Node Experimental Cluster for Computer $90 of each member’s annual dues is for a Systems Research subscription to ;login:. Subscriptions for non- Garth Gibson, Gary Grider, Andree Jacobson, and Wyatt Lloyd members are $90 per year. Periodicals postage paid at Berkeley, CA, and additional offices. HARDWARE POSTMASTER: Send address changes to ;login:, USENIX Association, 2560 Ninth Street, 40 Programming Models for Emerging Non-Volatile Suite 215, Berkeley, CA 94710. Memory Technologies ©2013 USENIX Association Andy Rudoff USENIX is a registered trademark of the USENIX Association. Many of the designations used by manufacturers and sellers to COLUMNS distinguish their products are claimed 46 Practical Perl Tools David Blank-Edelman as trademarks. USENIX acknowledges all trademarks herein. Where those designations 50 A PyCon Notebook David Beazley appear in this publication and USENIX is aware of a trademark claim, the designations have 55 iVoyeur Dave Josephsen been printed in caps or initial caps. 58 For Good Measure Dan Geer and Dan Conway 61 /dev/random Robert G. Ferrell 64 Notes BOOKS 66 Book Reviews Mark Lamourine and Trey Darley CONFERENCE REPORTS 69 11th USENIX Conference on File and Storage Technologies (FAST ’13) Musings RIK FARROWEDITORIAL Rik is the editor of ;login:. he trouble with the future is that it never arrives. For me, there is only [email protected] right now, with an imagined future some constant distance away in Tthe, uh, future. But things do change. I love attending FAST, because some of my own roots are on the vendor side, and FAST provides one of the best blends of academic and vendor research of any USENIX conference. FAST ’13 was no exception, and when Rick Wheeler suggested I attend a particular BoF (one I might have skipped), I discovered something interesting. A Game Changer? Andy Rudoff, now with Intel, once a Sun engineer, was already well into his presenta- tion when I wandered in. Andy was enthusiastic, that was certain. But would Non-Volatile Memory (NVM) really be the game changer that he was hinting at? Not that Andy was really hinting at anything. His presentation, and his article in this issue, was about adding two new interfaces for NVM. We already have two interfaces for NVM, in the now familiar form of SSDs: a block and a file interface. What Andy was explaining relies on there being a form of NVM that is addressable at the byte level, instead of the block level, as with current Flash devices. This suggestion got my attention. During HotOS 2011, Katelin Bailey presented a position paper about systems built with NVM [1]. Imagine a system with gigabytes of byte-address- able persistent memory. If you hibernate such a system, it can sleep using no power, but wake up immediately with all its memory intact. You don’t need virtual memory, because you don’t need to use disk for backing limited DRAM. But there are also problems with this picture. For example, now we can safely assume that rebooting a system clears memory (well, almost [2]), but if DRAM is replaced with NVM, that assumption is no longer true; whatever got us into trouble before is still there. Andy suggests two new interfaces to byte-addressable NVM: PM (persistent memory) Volume Mode and PM File Mode. Although these might sound similar to the current ways we have for accessing Flash, they are different in that they assume the CPU can perform load/ store instructions at the byte level, which is very different from the block-oriented Flash we’ve been learning about and using for years. In an interview [3], Intel’s Chief Technology Officer, Justin Rattner, said that new NVM will have low latency, in the tens of nanoseconds. Just compare that to typical disk latency, which is measured in milliseconds. Well, let’s see: nanosecond = 10-9 vs. millisecond = 10-3 That would be quite a difference. I tried to pry more from Andy about just how much NVM we might expect to have, but he couldn’t tell me—or if he could, I couldn’t tell you. You know, the usual NDA conundrum. But my suspicion is that NVM could be a real game changer, if the various technologies for creating this memory actually prove capable of being used in cheap, reliable, fast, and dense devices. 2 JUNE 2013 VOL. 38 NO. 3 www.usenix.org EDITORIAL Musings Shingles, Not on a Roof believe) write-once; if SMR drives could provide better perfor- Not that I am expecting terabytes (or tebibytes [4]) of affordable mance, if 64 MB bands were used instead of using ext4, I think PM anytime soon. Hard disk drives (HDDs) have managed to that Google just might be interested. grow in capacity at a rate of about 40% a year. But this growth is Many years ago, a friend who worked on IBM mainframes in a going to hit a wall soon, as the ability to write sectors to ever nar- bank let me look at some of their documentation.
Load more

Recommended publications
  • Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4
    SUSE Linux Enterprise Server 12 SP4 Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4 Provides information about how to manage storage devices on a SUSE Linux Enterprise Server. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xii 2 Giving Feedback xiv 3 Documentation Conventions xiv 4 Product Life Cycle and Support xvi Support Statement for SUSE Linux Enterprise Server xvii • Technology Previews xviii I FILE SYSTEMS AND MOUNTING 1 1 Overview
    [Show full text]
  • Z/OS Distributed File Service Zseries File System Implementation Z/OS V1R13
    Front cover z/OS Distributed File Service zSeries File System Implementation z/OS V1R13 Defining and installing a zSeries file system Performing backup and recovery, sysplex sharing Migrating from HFS to zFS Paul Rogers Robert Hering ibm.com/redbooks International Technical Support Organization z/OS Distributed File Service zSeries File System Implementation z/OS V1R13 October 2012 SG24-6580-05 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. Sixth Edition (October 2012) This edition applies to version 1 release 13 modification 0 of IBM z/OS (product number 5694-A01) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2010, 2012. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xiii Trademarks . xiv Preface . .xv The team who wrote this book . .xv Now you can become a published author, too! . xvi Comments welcome. xvi Stay connected to IBM Redbooks . xvi Chapter 1. zFS file systems . 1 1.1 zSeries File System introduction. 2 1.2 Application programming interfaces . 2 1.3 zFS physical file system . 3 1.4 zFS colony address space . 4 1.5 zFS supports z/OS UNIX ACLs. 4 1.6 zFS file system aggregates. 5 1.6.1 Compatibility mode aggregates. 5 1.6.2 Multifile system aggregates. 6 1.7 Metadata cache. 7 1.8 zFS file system clones . 7 1.8.1 Backup file system . 8 1.9 zFS log files.
    [Show full text]
  • Configuring and Managing the Network File System
    ch33.fm Page 639 Saturday, April 29, 2000 1:41 AM THIRTY-THREE 33 Configuring and Managing the Network File System LChapter Syllabus The Network File System (NFS) is used to share files and directories over a network. It is an RPC- 33.1 NFS Concepts based system and works in the client-server model. The NFS server makes some of its file sys- 33.2 Configuring an NFS Server tems shareable with other systems on a network. The NFS client mounts shared file systems from 33.3 Configuring an NFS Client the server to its local mount points. Users of the client machines can use NFS-mounted file systems 33.4 NFS Daemons just like the local file systems. NFS support is available on many platforms including personal 33.5 Troubleshooting computers. On UNIX systems, this has become a de facto standard and provides a transparent way for sharing files. When used in combination with NIS, it facilitates users’ logging in from any machine on the network and finding the same environment, home directories, and mailboxes. NFS is used to save disk space in a number of ways. All files that are static in nature can be shared on a network. These files include applica- tion directories under /opt and operating system files under the /usr directory. The files that are 639 ch33.fm Page 640 Saturday, April 29, 2000 1:41 AM 640 Chapter 33 • Configuring and Managing the Network File System shared by individual users are users’ home directories and mail- boxes. The directories that contain configuration files or log files are usually not shared.
    [Show full text]
  • GPFS Policy Engine
    General Parallel File System Version 4 Release 1 Administration and Programming Reference SA23-1452-00 General Parallel File System Version 4 Release 1 Administration and Programming Reference SA23-1452-00 Note Before using this information and the product it supports, read the information in “Notices” on page 655. This edition applies to version 4 release 1 modification 0 of the following products, and to all subsequent releases and modifications until otherwise indicated in new editions: v IBM General Parallel File System ordered through Passport Advantage® (product number 5725-Q01) v IBM General Parallel File System ordered through AAS/eConfig (product number 5641-GPF) v IBM General Parallel File System ordered through HVEC/Xcel (product number 5641-GP6, 5641-GP7, or 5641-GP8) Significant changes or additions to the text and illustrations are indicated by a vertical line (|) to the left of the change. IBM welcomes your comments; see the topic “How to send your comments” on page xii. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Tables ...............vii Backing up a file system using the mmbackup command ..............34 About this information ........ix Backing up a file system using the GPFS policy engine ...............40 Prerequisite and related information ......x Backing up file system configuration information 40 Conventions used in this information ......xi Using APIs to develop backup applications.
    [Show full text]
  • Managing Network File Systems in Oracle® Solaris 11.4
    Managing Network File Systems in ® Oracle Solaris 11.4 Part No: E61004 August 2021 Managing Network File Systems in Oracle Solaris 11.4 Part No: E61004 Copyright © 2002, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Introduction to Distributed File Systems. Orangefs Experience 0.05 [Width=0.4]Lvee-Logo-Winter
    Introduction to distributed file systems. OrangeFS experience Andrew Savchenko NRNU MEPhI, Moscow, Russia 16 February 2013 . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Outline 1. Introduction 2. Species of distributed file systems 3. Behind the curtain 4. OrangeFS 5. Summary . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Introduction Why one needs a non-local file system? • a large data storage • a high performance data storage • redundant and highly available solutions There are dozens of them: 72 only on wiki[1], more IRL. Focus on free software solutions. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Introduction Why one needs a non-local file system? • a large data storage • a high performance data storage • redundant and highly available solutions There are dozens of them: 72 only on wiki[1], more IRL. Focus on free software solutions. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Species of distributed file systems Network Clustered Distributed Terminology is ambiguous!. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Network file systems client1 client2 clientN server storage A single server (or at least an appearance) and multiple network clients. Examples: NFS, CIFS. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Clustered file systems server1 server2 serverN storage Servers sharing the same local storage (usually SAN[2] at block level). shared storage architecture. Examples: GFS2[3], OCFS2[4]. .. .. .. .. .
    [Show full text]
  • Ted Ts'o on Linux File Systems
    Ted Ts’o on Linux File Systems An Interview RIK FARROW Rik Farrow is the Editor of ;login:. ran into Ted Ts’o during a tutorial luncheon at LISA ’12, and that later [email protected] sparked an email discussion. I started by asking Ted questions that had I puzzled me about the early history of ext2 having to do with the perfor- mance of ext2 compared to the BSD Fast File System (FFS). I had met Rob Kolstad, then president of BSDi, because of my interest in the AT&T lawsuit against the University of California and BSDi. BSDi was being sued for, among other things, Theodore Ts’o is the first having a phone number that could be spelled 800-ITS-UNIX. I thought that it was important North American Linux for the future of open source operating systems that AT&T lose that lawsuit. Kernel Developer, having That said, when I compared the performance of early versions of Linux to the current version started working with Linux of BSDi, I found that they were closely matched, with one glaring exception. Unpacking tar in September 1991. He also archives using Linux (likely .9) was blazingly fast compared to BSDi. I asked Rob, and he served as the tech lead for the MIT Kerberos explained that the issue had to do with synchronous writes, finally clearing up a mystery for me. V5 development team, and was the architect at IBM in charge of bringing real-time Linux Now I had a chance to ask Ted about the story from the Linux side, as well as other questions in support of real-time Java to the US Navy.
    [Show full text]
  • CS 416: Operating Systems Design March 25, 2015
    CS 416: Operating Systems Design March 25, 2015 Operating Systems Terminology 13. File Systems Paul Krzyzanowski Rutgers University Spring 2015 3/25/2015 © 2014-2015 Paul Krzyzanowski 1 What’s a file system? Terms • Traditionally • Disk – A way to manage variable-size persistent data – Non-volatile block-addressable storage. • Organize, store, retrieve, delete information • Block = sector – Random access – Smallest chunk of I/O on a disk • Arbitrary files can be accessed by name • Arbitrary parts of a file can be accessed – Common block sizes = 512 or 4096 (4K) bytes E.g., WD Black Series 4TB drive has 7,814,037,168 512-byte sectors – File systems are implemented on top of block devices • Partition – Set of contiguous blocks on a disk. A disk has ≥ 1 partitions • More abstract – A way to access information by name • Volume • Devices – Disk, disks, or partition that contains a file system • System configuration, process info, random numbers – A volume may span disks 3 4 More terms File Terms • Track • File – Blocks are stored on concentric tracks on a disk – A unit of data managed by the file system • Cylinder • Data: (Contents) – The set of all blocks on one track – The user data associated with a file (obsolete now since we don’t know what’s where) – Unstructured (byte stream) or structured (records) • Seek • Name – The movement of a disk head from track to track – A textual name that identifies the file 5 © 2014-2015 Paul Krzyzanowski 1 CS 416: Operating Systems Design March 25, 2015 File Terms File System Terms • Metadata • Superblock
    [Show full text]
  • File Allocation Table - Wikipedia, the Free Encyclopedia Page 1 of 22
    File Allocation Table - Wikipedia, the free encyclopedia Page 1 of 22 File Allocation Table From Wikipedia, the free encyclopedia File Allocation Table (FAT) is a file system developed by Microsoft for MS-DOS and is the primary file system for consumer versions of Microsoft Windows up to and including Windows Me. FAT as it applies to flexible/floppy and optical disc cartridges (FAT12 and FAT16 without long filename support) has been standardized as ECMA-107 and ISO/IEC 9293. The file system is partially patented. The FAT file system is relatively uncomplicated, and is supported by virtually all existing operating systems for personal computers. This ubiquity makes it an ideal format for floppy disks and solid-state memory cards, and a convenient way of sharing data between disparate operating systems installed on the same computer (a dual boot environment). The most common implementations have a serious drawback in that when files are deleted and new files written to the media, directory fragments tend to become scattered over the entire disk, making reading and writing a slow process. Defragmentation is one solution to this, but is often a lengthy process in itself and has to be performed regularly to keep the FAT file system clean. Defragmentation should not be performed on solid-state memory cards since they wear down eventually. Contents 1 History 1.1 FAT12 1.2 Directories 1.3 Initial FAT16 1.4 Extended partition and logical drives 1.5 Final FAT16 1.6 Long File Names (VFAT, LFNs) 1.7 FAT32 1.8 Fragmentation 1.9 Third party
    [Show full text]
  • Red Hat Enterprise Linux 6 Storage Administration Guide
    Red Hat Enterprise Linux 6 Storage Administration Guide Deploying and configuring single-node storage in Red Hat Enterprise Linux 6 Josef Bacik Kamil Dudka Hans de Goede Doug Ledford Daniel Novotny Storage Administration Guide Nathan Straz David Wysochanski Michael Christie Sachin Prabhu Rob Evers David Howells David Lehman Jeff Moyer Eric Sandeen Mike Snitzer Red Hat Enterprise Linux 6 Storage Administration Guide Deploying and configuring single-node storage in Red Hat Enterprise Linux 6 Edition 0 Author Josef Bacik [email protected] Author Kamil Dudka [email protected] Author Hans de Goede [email protected] Author Doug Ledford [email protected] Author Daniel Novotny [email protected] Author Nathan Straz [email protected] Author David Wysochanski [email protected] Author Michael Christie [email protected] Author Sachin Prabhu [email protected] Author Rob Evers [email protected] Author David Howells [email protected] Author David Lehman [email protected] Author Jeff Moyer [email protected] Author Eric Sandeen [email protected] Author Mike Snitzer [email protected] Editor Don Domingo [email protected] Copyright © 2010 Red Hat Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
    [Show full text]
  • Managing Network File Systems in Oracle® Solaris 11.3
    Managing Network File Systems in ® Oracle Solaris 11.3 Part No: E54789 September 2018 Managing Network File Systems in Oracle Solaris 11.3 Part No: E54789 Copyright © 2002, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • File Systems and Storage
    File Systems and Storage Rich Sudlow and Paul Brenner University of Notre Dame Center for Research Computing Last Modified : 06/22/11 Last Modified : 06/22/11 Overview • File System Concepts – Aspects and Types – Why do we have so many? • Redundancy and Performance – RAID – Examples on X4500 “thumper” • CRC Supported File Systems – Centralized (ext3, fat32/ntfs) – Distributed (AFS, NFS) – Comparision – capabilities • AFS – crc.nd.edu, nd.edu cells • Backup Storage – Software, Cache, Tape Silo • Using CRC Storage – Scratch space, User workspace, Backup Last Modified : 06/22/11 3 Disclaimer • This is: – A broad overview – Operational viewpoint – Starting point • This is not: – Comprehensive – Authoritative analysis of the industry/technology • For more info consider: – ND courses relevant to this topic – Contacting CRC for specific individual requirements Last Modified : 06/22/11 4 File Systems Concepts • Aspects – Filenames – Meta data (size, # blocks, time, security) – Hierarchical vs Flat – Secure access – Capabilities/Facilities (move, delete, append) – Why so many? Why not use just one? • Types – Disk/Flash – Database & Transactional – Network/Distributed Last Modified :– 06/22/11Special Purpose 5 Wikipedia – List of File Systems http://en.wikipedia.org/wiki/List_of_file_systems Last Modified : 06/22/11 6 Redundancy and Performance • File system design is strongly influenced by the target feature set – Bandwidth, security, latency, distributed access, fault tolerance, etc... • File systems can be tuned and tiered to exploit feature
    [Show full text]