GPFS Policy Engine

Total Page:16

File Type:pdf, Size:1020Kb

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. 40 How to send your comments ........xii Scale Out Backup and Restore (SOBAR) .....41 || Summary of changes ........xiii Chapter 4. Managing disks ......43 Displaying disks in a GPFS cluster ......43 Chapter 1. Performing GPFS Adding disks to a file system ........44 administration tasks .........1 Deleting disks from a file system .......44 Requirements for administering a GPFS file system . 1 Replacing disks in a GPFS file system .....46 adminMode configuration parameter .....2 Additional considerations for managing disks . 47 Common GPFS command principles ......3 Displaying GPFS disk states .........48 Specifying nodes as input to GPFS commands . 3 Disk availability ............48 Stanza files ..............4 Disk status .............48 Changing GPFS disk states and parameters....49 Chapter 2. Managing your GPFS cluster 7 Changing your NSD configuration.......50 Creating your GPFS cluster .........7 Changing NSD server usage and failback ....51 Displaying GPFS cluster configuration information . 7 Enabling and disabling Persistent Reserve ....52 Adding nodes to a GPFS cluster ........8 Deleting nodes from a GPFS cluster ......9 Chapter 5. Managing GPFS quotas. 53 Changing the GPFS cluster configuration data . 10 Enabling and disabling GPFS quota management. 53 Node quorum considerations ........18 Default quotas .............54 Node quorum with tiebreaker considerations . 18 Explicitly establishing and changing quotas . 55 Displaying and changing the file system manager Checking quotas.............56 node.................18 Listing quotas .............57 Determining how long mmrestripefs takes to Activating quota limit checking........58 complete ...............19 Deactivating quota limit checking .......59 Starting and stopping GPFS .........20 Changing the scope of quota limit checking . 59 Creating file system quota reports .......60 Chapter 3. Managing file systems . 23 Restoring quota files ...........60 Mounting a file system ..........23 Mounting a file system on multiple nodes . 23 Chapter 6. Managing GPFS access GPFS-specific mount options .......23 control lists and NFS export .....63 Unmounting a file system .........25 Traditional GPFS ACL administration......63 Unmounting a file system on multiple nodes . 25 Setting traditional GPFS access control lists . 64 Deleting a file system ...........25 Displaying traditional GPFS access control lists 65 Determining which nodes have a file system Applying an existing traditional GPFS access mounted ...............26 control list ..............65 Checking and repairing a file system ......26 Changing traditional GPFS access control lists . 66 Listing file system attributes .........28 Deleting traditional GPFS access control lists . 66 Modifying file system attributes .......29 NFS V4 ACL administration .........66 Querying and changing file replication attributes . 29 NFS V4 ACL Syntax ..........67 Querying file replication .........29 NFS V4 ACL translation .........69 Changing file replication attributes .....29 Setting NFS V4 access control lists......69 Using Direct I/O on a file in a GPFS file system . 30 Displaying NFS V4 access control lists ....70 Restriping a GPFS file system ........30 Applying an existing NFS V4 access control list 70 Querying file system space .........31 Changing NFS V4 access control lists .....70 Querying and reducing file system fragmentation . 32 Deleting NFS V4 access control lists .....70 Querying file system fragmentation .....33 Considerations when using GPFS with NFS V4 Reducing file system fragmentation .....33 ACLs ...............71 Backing up a file system ..........34 NFS and GPFS .............71 Exporting a GPFS file system using NFS....71 © Copyright IBM Corp. 2014 iii NFS usage of GPFS cache.........74 mmdelnode command ..........288 || Local read-only cache ..........74 || mmdelnodeclass command .........291 Synchronous writing using NFS ......75 mmdelnsd command ...........293 Unmounting a file system after NFS export. 75 mmdelpdisk command ..........295 NFS automount considerations .......75 mmdelrecoverygroup command .......298 Clustered NFS and GPFS on Linux .....75 mmdelsnapshot command .........300 mmdelvdisk command ..........302 Chapter 7. GPFS commands .....77 mmdf command ............304 mmaddcallback command .........82 mmdiag command ...........307 mmaddcomp command ..........92 mmdiscovercomp command ........312 mmadddisk command...........95 mmeditacl command ...........314 mmaddnode command ..........101 mmedquota command ..........317 mmaddpdisk command ..........104 mmexportfs command ..........321 || mmafmconfig command..........106 mmfsck command............323 mmafmctl command ...........108 mmfsctl command............328 mmafmlocal command ..........115 mmgetacl command ...........332 mmapplypolicy command .........117 mmgetstate command ..........335 mmauth command ...........126 mmimgbackup command .........338 mmbackup command ..........131 mmimgrestore command .........341 mmbackupconfig command ........138 mmimportfs command ..........344 mmchattr command ...........140 mmlinkfileset command ..........348 mmchcarrier command ..........145 mmlsattr command ...........350 mmchcluster command ..........148 mmlscallback command ..........353 mmchcomp command ..........152 mmlscluster command ..........355 mmchcomploc command .........155 mmlscomp command...........357 mmchconfig command ..........157 mmlscomploc command..........360 mmchdisk command ...........176 mmlscompspec command .........362 mmcheckquota command .........181 mmlsconfig command ..........364 mmchenclosure command .........184 mmlsdisk command ...........366 mmchfileset command ..........186 mmlsenclosure command .........369 mmchfirmware command .........191 mmlsfileset command ..........372 mmchfs command............194 mmlsfirmware command .........376 mmchlicense command ..........199 mmlsfs command ............378 mmchmgr command ...........201 mmlslicense command ..........382 mmchnode command ..........203 mmlsmgr command ...........384 || mmchnodeclass command .........207 mmlsmount command ..........386 mmchnsd command ...........210 || mmlsnodeclass command .........388 mmchpdisk command ..........213 mmlsnsd command ...........391 mmchpolicy command ..........215 mmlspdisk command...........394 mmchpool command ...........217 mmlspolicy command ..........397 mmchrecoverygroup command .......219 mmlspool command ...........399 mmclone command ...........221 mmlsquota command ..........401 mmcrcluster command ..........224 mmlsrecoverygroup command .......405 mmcrfileset command ..........228 mmlsrecoverygroupevents command .....408 mmcrfs command ............233 mmlssnapshot command .........410 || mmcrnodeclass command .........242 mmlsvdisk command...........412 mmcrnsd command ...........244 mmmigratefs command ..........415 mmcrrecoverygroup command .......249 mmmount command ...........417 mmcrsnapshot command .........252 mmnsddiscover command .........419 mmcrvdisk command ..........255 mmpmon command ...........421 mmdefedquota command .........260 mmpsnap command ...........426 mmdefquotaoff command .........263 mmputacl command ...........429 mmdefquotaon command .........266 mmquotaoff command ..........432 mmdefragfs command ..........270 mmquotaon command ..........434 mmdelacl command ...........273 mmremotecluster command ........437 mmdelcallback command .........275 mmremotefs command ..........440 mmdelcomp command ..........276 mmrepquota command ..........443 mmdelcomploc command .........278 mmrestoreconfig command.........447 mmdeldisk command ..........280 mmrestorefs command ..........451 mmdelfileset command ..........283 mmrestripefile command .........455 mmdelfs command ...........286 mmrestripefs command ..........458 iv GPFS: Administration and Programming Reference mmrpldisk
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]
  • 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]
  • 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
    [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 rik@usenix.org 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 jwhiter@redhat.com Author Kamil Dudka kdudka@redhat.com Author Hans de Goede hdegoede@redhat.com Author Doug Ledford dledford@redhat.com Author Daniel Novotny dnovotny@redhat.com Author Nathan Straz nstraz@redhat.com Author David Wysochanski dwysocha@redhat.com Author Michael Christie mchristi@redhat.com Author Sachin Prabhu sprabhu@redhat.com Author Rob Evers revers@redhat.com Author David Howells dhowells@redhat.com Author David Lehman dlehman@redhat.com Author Jeff Moyer jmoyer@redhat.com Author Eric Sandeen esandeen@redhat.com Author Mike Snitzer msnitzer@redhat.com Editor Don Domingo ddomingo@redhat.com 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]