DOCSLIB.ORG

New/Usr/Src/Common/Zfs/Zfs Prop.C 1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
New/Usr/Src/Common/Zfs/Zfs Prop.C 1 new/usr/src/common/zfs/zfs_prop.c 1 new/usr/src/common/zfs/zfs_prop.c 2 ********************************************************** 61 #include <string.h> 13892 Wed Jan 31 21:21:15 2007 62 #include <ctype.h> new/usr/src/common/zfs/zfs_prop.c 63 #endif 1000002 gzip compression for ZFS ********************************************************** 65 typedef enum { 1 /* 66 prop_default, 2 * CDDL HEADER START 67 prop_readonly, 3 * 68 prop_inherit 4 * The contents of this file are subject to the terms of the 69 } prop_attr_t; 5 * Common Development and Distribution License (the "License"). ______unchanged_portion_omitted_ 6 * You may not use this file except in compliance with the License. 7 * 83 static prop_desc_t zfs_prop_table[ZFS_NPROP_ALL] = { 8 * You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 84 { "type", prop_type_string, 0, NULL, prop_readonly, 9 * or http://www.opensolaris.org/os/licensing. 85 ZFS_TYPE_ANY, "filesystem | volume | snapshot", "TYPE", B_TRUE }, 10 * See the License for the specific language governing permissions 86 { "creation", prop_type_number, 0, NULL, prop_readonly, 11 * and limitations under the License. 87 ZFS_TYPE_ANY, "<date>", "CREATION", B_FALSE }, 12 * 88 { "used", prop_type_number, 0, NULL, prop_readonly, 13 * When distributing Covered Code, include this CDDL HEADER in each 89 ZFS_TYPE_ANY, "<size>", "USED", B_TRUE }, 14 * file and include the License file at usr/src/OPENSOLARIS.LICENSE. 90 { "available", prop_type_number, 0, NULL, prop_readonly, 15 * If applicable, add the following below this CDDL HEADER, with the 91 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_VOLUME, "<size>", "AVAIL", B_TRUE }, 16 * fields enclosed by brackets "[]" replaced with your own identifying 92 { "referenced", prop_type_number, 0, NULL, prop_readonly, 17 * information: Portions Copyright [yyyy] [name of copyright owner] 93 ZFS_TYPE_ANY, 18 * 94 "<size>", "REFER", B_TRUE }, 19 * CDDL HEADER END 95 { "compressratio", prop_type_number, 0, NULL, prop_readonly, 20 */ 96 ZFS_TYPE_ANY, "<1.00x or higher if compressed>", "RATIO", B_TRUE }, 21 /* 97 { "mounted", prop_type_boolean, 0, NULL, prop_readonly, 22 * Copyright 2007 Sun Microsystems, Inc. All rights reserved. 98 ZFS_TYPE_FILESYSTEM, "yes | no | -", "MOUNTED", B_TRUE }, 23 * Use is subject to license terms. 99 { "origin", prop_type_string, 0, NULL, prop_readonly, 24 */ 100 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_VOLUME, "<snapshot>", "ORIGIN", 101 B_FALSE }, 26 #pragma ident "@(#)zfs_prop.c 1.17 07/01/31 SMI" 102 { "quota", prop_type_number, 0, NULL, prop_default, 26 #pragma ident "@(#)zfs_prop.c 1.16 07/01/05 SMI" 103 ZFS_TYPE_FILESYSTEM, "<size> | none", "QUOTA", B_TRUE }, 104 { "reservation", prop_type_number, 0, NULL, prop_default, 28 /* 105 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_VOLUME, 29 * Master property table. 106 "<size> | none", "RESERV", B_TRUE }, 30 * 107 { "volsize", prop_type_number, 0, NULL, prop_default, 31 * This table keeps track of all the properties supported by ZFS, and their 108 ZFS_TYPE_VOLUME, "<size>", "VOLSIZE", B_TRUE }, 32 * various attributes. Not all of these are needed by the kernel, and several 109 { "volblocksize", prop_type_number, 8192, NULL, prop_readonly, 33 * are only used by a single libzfs client. But having them here centralizes 110 ZFS_TYPE_VOLUME, "512 to 128k, power of 2", "VOLBLOCK", B_TRUE }, 34 * all property information in one location. 111 { "recordsize", prop_type_number, SPA_MAXBLOCKSIZE, NULL, 35 * 112 prop_inherit, 36 * name The human-readable string representing this property 113 ZFS_TYPE_FILESYSTEM, 37 * proptype Basic type (string, boolean, number) 114 "512 to 128k, power of 2", "RECSIZE", B_TRUE }, 38 * default Default value for the property. Sadly, C only allows 115 { "mountpoint", prop_type_string, 0, "/", prop_inherit, 39 * you to initialize the first member of a union, so we 116 ZFS_TYPE_FILESYSTEM, 40 * have two default members for each property. 117 "<path> | legacy | none", "MOUNTPOINT", B_FALSE }, 41 * attr Attributes (readonly, inheritable) for the property 118 { "sharenfs", prop_type_string, 0, "off", prop_inherit, 42 * types Valid dataset types to which this applies 119 ZFS_TYPE_FILESYSTEM, 43 * values String describing acceptable values for the property 120 "on | off | share(1M) options", "SHARENFS", B_FALSE }, 44 * colname The column header for 'zfs list' 121 { "shareiscsi", prop_type_string, 0, "off", prop_inherit, 45 * colfmt The column formatting for 'zfs list' 122 ZFS_TYPE_ANY, 46 * 123 "on | off | type=<type>", "SHAREISCSI", B_FALSE }, 47 * This table must match the order of property types in libzfs.h. 124 { "checksum", prop_type_index, ZIO_CHECKSUM_DEFAULT, "on", 48 */ 125 prop_inherit, ZFS_TYPE_FILESYSTEM | ZFS_TYPE_VOLUME, 126 "on | off | fletcher2 | fletcher4 | sha256", "CHECKSUM", B_TRUE }, 50 #include <sys/zio.h> 127 { "compression", prop_type_index, ZIO_COMPRESS_DEFAULT, "off", 51 #include <sys/spa.h> 128 prop_inherit, ZFS_TYPE_FILESYSTEM | ZFS_TYPE_VOLUME, 52 #include <sys/zfs_acl.h> 129 "on | off | lzjb | gzip", "COMPRESS", B_TRUE }, 53 #include <sys/zfs_ioctl.h> 129 "on | off | lzjb", "COMPRESS", B_TRUE }, 130 { "atime", prop_type_boolean, 1, NULL, prop_inherit, 55 #include "zfs_prop.h" 131 ZFS_TYPE_FILESYSTEM, 132 "on | off", "ATIME", B_TRUE }, 57 #if defined(_KERNEL) 133 { "devices", prop_type_boolean, 1, NULL, prop_inherit, 58 #include <sys/systm.h> 134 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_SNAPSHOT, 59 #else 135 "on | off", "DEVICES", B_TRUE }, 60 #include <stdlib.h> 136 { "exec", prop_type_boolean, 1, NULL, prop_inherit, new/usr/src/common/zfs/zfs_prop.c 3 137 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_SNAPSHOT, 138 "on | off", "EXEC", B_TRUE }, 139 { "setuid", prop_type_boolean, 1, NULL, prop_inherit, 140 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_SNAPSHOT, "on | off", "SETUID", 141 B_TRUE }, 142 { "readonly", prop_type_boolean, 0, NULL, prop_inherit, 143 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_VOLUME, 144 "on | off", "RDONLY", B_TRUE }, 145 { "zoned", prop_type_boolean, 0, NULL, prop_inherit, 146 ZFS_TYPE_FILESYSTEM, 147 "on | off", "ZONED", B_TRUE }, 148 { "snapdir", prop_type_index, ZFS_SNAPDIR_HIDDEN, "hidden", 149 prop_inherit, 150 ZFS_TYPE_FILESYSTEM, 151 "hidden | visible", "SNAPDIR", B_TRUE }, 152 { "aclmode", prop_type_index, ZFS_ACL_GROUPMASK, "groupmask", 153 prop_inherit, ZFS_TYPE_FILESYSTEM, 154 "discard | groupmask | passthrough", "ACLMODE", B_TRUE }, 155 { "aclinherit", prop_type_index, ZFS_ACL_SECURE, "secure", 156 prop_inherit, ZFS_TYPE_FILESYSTEM, 157 "discard | noallow | secure | passthrough", "ACLINHERIT", B_TRUE }, 158 { "canmount", prop_type_boolean, 1, NULL, prop_default, 159 ZFS_TYPE_FILESYSTEM, 160 "on | off", "CANMOUNT", B_TRUE }, 161 { "xattr", prop_type_boolean, 1, NULL, prop_inherit, 162 ZFS_TYPE_FILESYSTEM | ZFS_TYPE_SNAPSHOT, 163 "on | off", "XATTR", B_TRUE }, 164 { "createtxg", prop_type_number, 0, NULL, prop_readonly, 165 ZFS_TYPE_ANY, NULL, NULL, B_FALSE}, 166 { "name", prop_type_string, 0, NULL, prop_readonly, 167 ZFS_TYPE_ANY, NULL, "NAME", B_FALSE }, 168 { "iscsioptions", prop_type_string, 0, NULL, prop_inherit, 169 ZFS_TYPE_VOLUME, NULL, "ISCSIOPTIONS", B_FALSE }, 170 { "numclones", prop_type_number, 0, NULL, prop_readonly, 171 ZFS_TYPE_SNAPSHOT, NULL, NULL, B_FALSE }, 172 }; ______unchanged_portion_omitted_ 321 static zfs_index_t compress_table[] = { 322 { "on", ZIO_COMPRESS_ON }, 323 { "off", ZIO_COMPRESS_OFF }, 324 { "lzjb", ZIO_COMPRESS_LZJB }, 325 { "gzip", ZIO_COMPRESS_GZIP }, 326 { NULL } 327 }; ______unchanged_portion_omitted_ new/usr/src/lib/libzpool/Makefile.com 1 new/usr/src/lib/libzpool/Makefile.com 2 ********************************************************** 60 C99MODE= -xc99=%all 2269 Wed Jan 31 21:21:15 2007 61 C99LMODE= -Xc99=%all new/usr/src/lib/libzpool/Makefile.com 1000002 gzip compression for ZFS 63 CFLAGS += -g $(CCVERBOSE) $(CNOGLOBAL) ********************************************************** 64 CFLAGS64 += -g $(CCVERBOSE) $(CNOGLOBAL) 1 # 65 LDLIBS += -lumem -lavl -lnvpair -lz -lc 2 # CDDL HEADER START 65 LDLIBS += -lumem -lavl -lnvpair -lc 3 # 66 CPPFLAGS += $(INCS) 4 # The contents of this file are subject to the terms of the 5 # Common Development and Distribution License (the "License"). 68 .KEEP_STATE: 6 # You may not use this file except in compliance with the License. 7 # 70 all: $(LIBS) 8 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 9 # or http://www.opensolaris.org/os/licensing. 72 lint: $(LINTLIB) 10 # See the License for the specific language governing permissions 11 # and limitations under the License. 74 include ../../Makefile.targ 12 # 13 # When distributing Covered Code, include this CDDL HEADER in each 76 pics/%.o: ../../../uts/common/fs/zfs/%.c 14 # file and include the License file at usr/src/OPENSOLARIS.LICENSE. 77 $(COMPILE.c) -o $@ $< 15 # If applicable, add the following below this CDDL HEADER, with the 78 $(POST_PROCESS_O) 16 # fields enclosed by brackets "[]" replaced with your own identifying 17 # information: Portions Copyright [yyyy] [name of copyright owner] 80 pics/%.o: ../../../common/zfs/%.c 18 # 81 $(COMPILE.c) -o $@ $< 19 # CDDL HEADER END 82 $(POST_PROCESS_O) 20 # 21 # 84 pics/%.o: ../../../uts/common/os/%.c 22 # Copyright 2007 Sun Microsystems, Inc. All rights reserved. 85 $(COMPILE.c) -o $@ $< 22 # Copyright 2006 Sun Microsystems, Inc. All rights reserved. 86 $(POST_PROCESS_O) 23 # Use is subject to license terms. 24 # 25 # ident "@(#)Makefile.com 1.4 07/01/31 SMI" 25 # ident "@(#)Makefile.com 1.3 06/08/03 SMI" 26 # 28 LIBRARY= libzpool.a 29 VERS= .1 31 # include the list of ZFS sources 32 include ../../../uts/common/Makefile.files
Load more

Recommended publications
  • C12) United States Patent (10) Patent No.: US 7,418,439 B2 Wong (45) Date of Patent: Aug
    111111 1111111111111111111111111111111111111111111111111111111111111 US007418439B2 c12) United States Patent (10) Patent No.: US 7,418,439 B2 Wong (45) Date of Patent: Aug. 26, 2008 (54) MIRROR FILE SYSTEM 5,870,734 A * 2/1999 Kao .............................. 707/2 5,873,085 A * 2/1999 Enoki eta!. ................... 707/10 (75) Inventor: John P. Wong, Fremont, CA (US) 5,946,685 A * 8/1999 Cramer eta!. ................ 707/10 6,000,020 A * 12/1999 Chin eta!. .................. 7111162 (73) Assignee: Twin Peaks Software, Inc., Fremont, 6,115,741 A * 9/2000 Domenikos et al .......... 709/217 CA (US) 6,192,408 B1 * 212001 Vahalia eta!. .............. 709/229 6,216,140 B1 * 4/2001 Kramer ...................... 715/511 6,298,390 B1 * 10/2001 Matena eta!. .............. 719/315 ( *) Notice: Subject to any disclaimer, the term of this 6,366,988 B1 * 4/2002 Skiba eta!. ................. 7111165 patent is extended or adjusted under 35 6,466,978 B1 * 10/2002 Mukherjee et al ........... 709/225 U.S.C. 154(b) by 1179 days. 6,625,750 B1 * 9/2003 Duso eta!. .................... 714/11 6,697,846 B1 * 2/2004 Soltis ......................... 709/217 (21) Appl. No.: 09/810,246 OTHER PUBLICATIONS (22) Filed: Mar. 19, 2001 Veritas User Manual, File Replicator™ 3 .0.1 for Solaris®, Jan. 2001, (65) Prior Publication Data pp. 1-115. US 2001/0051955 Al Dec. 13, 2001 * cited by examiner Primary Examiner-Sana Al-Hashemi Related U.S. Application Data (74) Attorney, Agent, or Firm-Buchanan Ingersoll & (60) Provisional application No. 60/189,979, filed on Mar. Rooney PC 17,2000. (57) ABSTRACT (51) Int.
    [Show full text]
  • System Administration Guide Devices and File Systems
    System Administration Guide: Devices and File Systems Part No: 817–5093–24 January 2012 Copyright © 2004, 2012, 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, the following notice is applicable: U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms setforth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
    [Show full text]
  • Solaris Internals
    SOLARIS INTERNALS Core Kernel Components i SOLARIS INTERNALS Core Kernel Components Jim Mauro and Richard McDougall Sun Microsystems Press A Prentice Hall Title © 2000 Sun Microsystems, Inc. — Printed in the United States of America. 901 San Antonio Road, Palo Alto, California 94303 U.S.A. All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authoriza- tion of Sun and its licensors, if any. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions as set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS—Sun, Sun Microsystems, the Sun logo, HotJava, Solaris, SunExpress, SunScreen, SunDocs, SPARC, SunOS, and SunSoft are trademarks or registered trademarks of Sun Microsystems, Inc. All other products or services mentioned in this book are the trademarks or service marks of their respective companies or organizations. 109 87654321 ISBN 0-13-022496-0 Sun Microsystems Press A Prentice Hall Title For Traci. .. for your love and encouragement .......................................... Richard For Donna, Frankie and Dominick. All my love, always... .......................................... Jim ACKNOWLEDGEMENTS It ‘s hard to thank all people that helped us with this book. As a minimum, we owe: • Thanks to Brian Wong, Adrian Cockcroft, Paul Strong, Lisa Musgrave and Fraser Gardiner for all your help and advise for the structure and content of this book.
    [Show full text]
  • Dell EMC Avamar Administration Guide
    Dell EMC Avamar Administration Guide 18.1 Dell Inc. June 2020 Rev. 04 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2001 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents Figures..........................................................................................................................................11 Tables.......................................................................................................................................... 12 Preface.........................................................................................................................................18 Chapter 1: Introduction.................................................................................................................. 21 Avamar system overview.................................................................................................................................................... 21 Avamar server.................................................................................................................................................................21 Avamar
    [Show full text]
  • SCO® Unixware® 2.1 Technical Summary
    SCO® UnixWare® 2.1 Technical Summary An SCO Technical White Paper February 1996 TM An SCO Technical White Paper Version 1.1 INTRODUCTION .......................................................................................................................................4 SCO UNIXWARE 2.1 STRENGTHS .......................................................................................................................................................5 WHAT’S NEW IN SCO UNIXWARE 2.1..................................................................................................................................................6 SCO UNIXWARE 2.1 PRODUCT LINE OVERVIEW .....................................................................................8 SCO UNIXWARE 2.1 SYSTEM OVERVIEW ..............................................................................................10 INSTALLATION REQUIREMENTS SCO UNIXWARE 2.1...............................................................................................................................10 APPLICATION SUPPORT .....................................................................................................................................................................10 THE SCO UNIXWARE 2.1 KERNEL: INSIDE A HIGH-PERFORMANCE ENGINE ..................................................................................................10 UnixWare 2.1 Symmetrical Multi-Processing and Threads ............................................................................... 11 SCO UnixWare
    [Show full text]
  • Downloaded for Free From
    The Design of the NetBSD I/O Subsystems SungWon Chung Pusan National University 2 This book is dedicated to the open-source code developers in the NetBSD community. The original copy of this publication is available in an electronic form and it can be downloaded for free from http://arXiv.org. Copyright (c) 2002 by SungWon Chung. For non-commercial and personal use, this publication may be reproduced, stored in a retrieval system, or transmitted in any form by any means, electronic, mechanical, photocopying, recording or otherwise. For commercial use, no part of this publication can be reproduced by any means without the prior written permission of the author. NetBSD is the registered trademark of The NetBSD Foundation, Inc. Contents Preface 14 I Basics to Learn Filesystem 15 1 Welcome to the World of Kernel ! 17 1.1 How Does a System Call Dive into Kernel from User Program ? . 17 1.1.1 Example: write system call . 17 1.1.2 Ultra SPARC 0x7c CPU Trap . 18 1.1.3 Jump to the File Descriptor Layer . 24 1.1.4 Arriving at Virtual Filesystem Operations . 28 1.2 General Data Structures in Kernel such as List, Hash, Queue, ... 30 1.2.1 Linked-Lists . 30 1.2.2 Tail Queues . 34 1.2.3 Hash . 38 1.3 Waiting and Sleeping in Kernel . 39 1.4 Kernel Lock Manager . 39 1.4.1 simplelock and lock . 39 1.4.2 Simplelock Interfaces . 40 1.4.3 Lock Interfaces . 40 1.5 Kernel Memory Allocation . 43 1.6 Resource Pool Manager .
    [Show full text]
  • HP-UX to Oracle Solaris Porting Guide Getting Started on the Move to Oracle Solaris
    An Oracle White Paper October 2011 HP-UX to Oracle Solaris Porting Guide Getting Started on the Move to Oracle Solaris HP-UX to Oracle Solaris Porting Guide Chapter 1 Introduction...................................................................... 1 Oracle Solaris ................................................................................. 1 The Advantages of Porting to Oracle Solaris.................................. 2 Chapter 2 The Porting Process........................................................ 4 Infrastructure and Application Porting Assessment ........................ 4 Build Environment Deployment....................................................... 5 Data Integration .............................................................................. 5 Source Code Porting....................................................................... 6 Application Verification.................................................................... 6 Commercial Applications and Third-Party Products ....................... 6 Chapter 3 Operating System Considerations................................... 7 Processor Endianness .................................................................... 7 Data Alignment ............................................................................... 7 Read/Write Structures..................................................................... 8 Storage Order and Alignment ......................................................... 8 64-Bit Data Models ........................................................................
    [Show full text]
  • Dell EMC Avamar Administration Guide
    Dell EMC Avamar Administration Guide 19.2 Dell Inc. June 2020 Rev. 04 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2001 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents Figures......................................................................................................................................... 12 Tables.......................................................................................................................................... 13 Preface........................................................................................................................................ 20 Chapter 1: Introduction..................................................................................................................23 Avamar system overview................................................................................................................................................... 23 Avamar server................................................................................................................................................................23 Avamar
    [Show full text]
  • Oracle Business Breakfast Oracle Solaris 11.4 Beta Jörg Möllenkamp Oracle Elite Engineering Exchange
    Oracle Business Breakfast Oracle Solaris 11.4 Beta Jörg Möllenkamp Oracle Elite Engineering Exchange V 0.13 21.03.2018 dd/jm Copyright Copyright © © 2018,2018,Oracle and/or its affiliates. All rights reserved. |Oracle and/or its affiliates. All rights reserved. Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 3 Scope What you can take away from this presentation? • How we will develop and deliver Oracle Solaris in the future. • Insight into the new and innovative features of Oracle Solaris 11.4 Beta • Practical command line examples you can try for yourself • No marketing slides. (unfortunately) Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 4 Oracle Solaris Strategy Best UNIX For Mission Critical WorkloaDs • Continuous Delivery Model – Innovation and critical fixes through dot releases, Quarterly Critical Patch Updates, and monthly Support Repository Updates • Secure and Stable – Integrated security and availability features to simplify deployments and operations • Oracle Database Integration – Data/systems management, networking, and performance features to enable optimal Oracle Database results on SPARC/Solaris Mission Critical Operating System Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 5 What Customers told us: Oracle Solaris Priorities A Non-disruptive stream of innovation • Consistent Operational Model • Operational Compatibility • Simple OS Deployment and Patching Methodology • Continuous Application Compatibility – No ISV Re-Qualification • Long support lifespan Copyright © 2018, Oracle and/or its affiliates.
    [Show full text]
  • Mac OS X Filesystems
    Mac OS X File Systems Had to give it a shot! Most ideas come from previous ideas. Alan Kay Looking Back This means that the return which is executed immediately after the call to aretu actually returns from the last routine which did the savu. They are not expected to understand this. You are not expected to understand this. UNIX The most important role of UNIX is to provide a file system. This means that the return which is executed immediately after the call to aretu actually returns from the last routine which did the savu. They are not expected to understand this. You are not expected to understand this. UNIX The most important Evroleerything of UNIX is ais file. to provide a file system. User Program User Kernel System Calls System Call Layer The File System User Program User Kernel System Calls System Call Layer Which? File System 1 File System 2 User Program User Kernel System Calls System Call Layer Which? FS1 FS2 FS3 ... FSn User Kernel Create() node 1 Remove() Read() ... node Write() n ... Some File System User Program User Kernel System Call Layer VNOP_CREATE() VNOP_REMOVE() ... ... v1 VNOP_READ() vn+1 VNOP_WRITE() ... vn vn+m Vnode/VFS hfs_create() ufs_create() h1 hfs_remove() u1 ufs_remove() ... ... hfs_read() ufs_read() hn hfs_write() um ufs_write() ... ... HFS+ UFS File Systems HFS+ AFP cddafs HFS SMB/CIFS devfs UFSManNFSy Filefdesc UDF WebDAV ISO9660SystemsFTP ZFS NTFS deadfs fifofs specfs MS-DOS synthfs union volfs ZFS Malloc/Free Abstraction No partitions (just storage pool) Automatically grows/shrinks Pool’s storage shared across file systems Transactional (no journal, no fsck) Copy-on-write, checksummed Inside HFS+ $ sudo hfsdebug -f -t 10 ..
    [Show full text]
  • File Systems
    Gregg.book Page 291 Wednesday, February 2, 2011 12:35 PM 5 File Systems File systems—an integral part of any operating system—have long been one of the most difficult components to observe when analyzing performance. This is largely because of the way file system data and metadata caching are implemented in the kernel but also because, until now, we simply haven’t had tools that can look into these kernel subsystems. Instead, we’ve analyzed slow I/O at the disk storage layer with tools such as iostat(1), even though this is many layers away from applica- tion latency. DTrace can be used to observe exactly how the file system responds to applications, how effective file system tuning is, and the internal operation of file system components. You can use it to answer questions such as the following. What files are being accessed, and how? By what or whom? Bytes, I/O counts? What is the source of file system latency? Is it disks, the code path, locks? How effective is prefetch/read-ahead? Should this be tuned? As an example, rwsnoop is a DTrace-based tool, shipping with Mac OS X and OpenSolaris, that you can use to trace read and write system calls, along with the filename for file system I/O. The following shows sshd (the SSH daemon) accept- ing a login on Solaris: # rwsnoop UID PID CMD D BYTES FILE 0 942611 sshd R 70 <unknown> 0 942611 sshd R 0 <unknown> continues 291 Gregg.book Page 292 Wednesday, February 2, 2011 12:35 PM 292 Chapter 5 File Systems 0 942611 sshd R 1444 /etc/gss/mech 0 942611 sshd R 0 /etc/gss/mech 0 942611 sshd R 0
    [Show full text]
  • 28. Óra Formázás, Fontosabb Fájlrendszerek
    2017.03.30 Összeállította: Szeli Márk 28. óra Formázás, fontosabb fájlrendszerek Formázás: A lemezformattálás (angolul disk formatting) vagy csak egyszerűen formattálás a számítástechnikában az az eljárás, ami a mágneses adattároló eszközt (merevlemezt, hajlékonylemezt) előkészíti a használatra. Amíg egy merevlemez partíció vagy egy hajlékonylemez nincs formattálva, addig nem alkalmas fájlok tárolására. Szintjei: Kétféle formázás létezik: Az alacsony szintű formattálás (low-level formatting) létrehozza a lemezeken a szektorokat, tehát kialakítja a winchester lemezeinek felszínén, hogy a szektorok hol kezdődjenek, és hol végződjenek – ez határozza meg, hogy a lemezeken hol lesznek majd tárolhatóak adatok. Ez a folyamat több órányi időt igénybe vehet, és következményeképpen a lemezen tárolt adatok – már amennyiben léteznek – megsemmisülnek. Az alacsony szintű formattálás nem csak egy partícióra, hanem a merevlemez teljes tárolásra alkalmas területére vonatkozik. Az alacsony szintű formattálást a winchester gyártók végzik, ugyanis nem megfelelő végrehajtása könnyen tönkretehetné a teljes merevlemezt. Az alacsony szintű formattálás után a merevlemez még nem alkalmas adatok (fájlok) tárolására; ehhez még magas szintű formattálás is szükséges. A magas szintű formattálás (high-level formatting) vagy logikai formattálás (logical formatting) az a folyamat, melynek során az operációs rendszer felkészít egy partíciót egy bizonyos fájlrendszer használatára. A logikai formattálás a partíción létrehozza a boot szektort, a fájlszervezési táblát (például
    [Show full text]