DOCSLIB.ORG

ZFS — and Why You Need It

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ZFS — and Why You Need It ZFS | and why you need it Nelson H. F. Beebe and Pieter J. Bowman University of Utah Department of Mathematics 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Email: [email protected], [email protected] 10 November 2016 Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 1 / 26 What is ZFS? Zettabyte File System (ZFS) developed by Sun Microsystems from 2001 to 2005, with open-source release in 2005 (whence OpenZFS project): SI prefix zetta ≡ 10007 = 1021 Sun Microsystems acquired in 2010 by Oracle [continuing ZFS] ground-up brand-new filesystem design exceptionally clean and well-documented source code enormous capacity 28 ≈ 255 bytes per filename 248 ≈ 1014 files per directory 264 ≈ 1018 bytes per file [1 exabyte] 78 23 1 2 ≈ 10 ≈ 2 Avogadro's number bytes per volume disks form a pool of storage that is always consistent on disk disk blocks in pool allocatable to any filesystem using pool [relatively] simple management optional dynamic quota adjustment ACLs, snapshots, clones, compression, encryption, deduplication, case-[in]sensitive filenames, Unicode filenames, . Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 2 / 26 Why use ZFS? ZFS provides a stable flexible filesystem of essentially unlimited capacity [in current technology] for decades to come we have run ZFS under Solaris for 11+ years, with neither data loss, nor filesystem corruption easy to implement n-way live mirroring [n up to 12 (??limit??)] snapshots, even in large filesystems, take only a second or so optional hot spares in each storage pool with ZFS zpool import, a filesystem can be moved to a different server, even one running a different O/S, as long as ZFS feature levels permit ZFS filesystems can be exported via FC, iSCSI, NFS (v2{v4) or SMB/CIFS to other systems, including those without native support for ZFS blocksize can be set in powers-of-two from 29 = 512 to 217 = 128K or with large blocks feature, to 220 = 1M; default on all systems is 128K. small files are stored in 512-byte sub-blocks of disk blocks Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 3 / 26 Where do we run ZFS? Solaris ( main filesystem for 10,000+ users Dyson ( fork of illumos and OpenSolaris with Debian GNU toolset FreeBSD FreeNAS and TrueNAS ( products of iXsystems GhostBSD ( fork of FreeBSD 10.3 GNU/Linux CentOS ( unsupported Red Hat GNU/Linux Debian GNU/Linux Ubuntu Hipster ( rolling update of OpenIndiana Illumian ( fork of OpenSolaris 11 illumos Mac OS X ( from OpenZFS, not from Apple OmniOS ( fork of OpenSolaris 11 illumos OpenIndiana ( fork of OpenSolaris 11 illumos PC-BSD ( fork of FreeBSD 10.3 Tribblix ( fork of illumos, OpenIndiana, and OpenSolaris TrueOS ( rolling-update successor to PC-BSD XStreamOS ( fork of OpenSolaris 11 illumos Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 4 / 26 zfs subcommands allow rename clone rollback create send destroy set get share groupspace snapshot inherit unallow mount unmount promote upgrade receive userspace # zfs snapshot tank/ROOT/initial@auto-`date +%Y-%m-%d` # zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT tank/ROOT/initial@auto-2016-09-13 136M - 16.8G - tank/ROOT/initial@auto-2016-09-19 304K - 16.9G - ... Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 5 / 26 zpool subcommands add iostat attach list clear offline create online destroy remove detach replace export scrub get set history status import upgrade # zpool iostat -v capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- tank 21.7G 56.3G 1 0 39.8K 3.58K ada0p2 21.7G 56.3G 1 0 39.8K 3.58K ---------- ----- ----- ----- ----- ----- ----- Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 6 / 26 ZFS storage pools zero or more hot spares allocated at pool-creation time, or later: # zpool create tank mirror c0t0d0 c0t1d0 spare c0t2d0 ( two disks in pool with one spare # zpool replace tank c0t0d0 c0t3d0 ( replace bad disk c0t0d0 # zpool remove tank c0t2d0 ( remove hot spare hot spares can be shared across multiple pools easy expansion: zpool add pool vdev disk-size agnostic [though best if pool members are identical] disk-vendor agnostic pools can grow, but cannot shrink optional quotas provide additional level of usage control within a pool quotas can oversubscribe pool storage quotas can grow or shrink: # zfs set quota=50G saspool01/students Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 7 / 26 ZFS data replication and recovery none (no media-failure protection) stripe over n disks (fast, but no media-failure protection) mirror: recover from failure of 1 of 2 disks triple-mirror: recover from failure of 2 of 3 disks RAID Z1: recover from failure of 1 of 4 or more disks RAID Z2: recover from failure of 2 of 9 or more disks RAID Z3: recover from failure of 3 of many disks Recoverable data errors result in replacement of the erroneous block, making ZFS self healing. Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 8 / 26 ZFS performance and reliability optional compression with LZJB, GZIP GZIP-2, or GZIP-9 algorithms compression may increase performance by reducing data transfer, as long as enough spare CPU cycles are available copy-on-write policy means that existing data blocks are never overwritten: once the new blocks are safely in place, old blocks are freed for re-use if they are not in a snapshot supports n-way mirrors: a mirror of n disks can lose up to n − 1 disks before data loss supports striping and RAID-Z[1-3] internal per-block checksums [no hardware RAID needed or desirable: JBOD is good enough because ZFS is better than RAID] ZFS is being optimized for SSDs, which suffer from severe wear limits that ultimately reduce disk and pool capacity Nelson H. F. Beebe and Pieter J. Bowman Why ZFS? 10 November 2016 9 / 26 ! *6J!.*JX!:'!E&N5+J!&6$#(*E(E!'%(!'/'*+!*-*&+*D+(!$$*5*$&'J!0/#!*++!0&+(EO!*++!E%*#(EO!*6F!*++!5#/K($'E!*EE/$&*'(F!.&'%!'%(! 5//+X! 123!G*'*!B#/'($'&/6! ;%(!,#*$+(!123!3'/#*4(!"55+&*6$(!5#/-&F(E!#/D)E'!F*'*!5#/'($'&/6!*'!D/'%!N&$#/E$/5&$!*6F!N*$#/E$/5&$!+(-(+EO! (6E)#&64!F*'*!&6'(4#&'J!*6F!5#/'($'&64!*4*&6E'!E&+(6'!F*'*!$/##)5'&/6!.%&+(!*+E/!5#/'($'&64!F*'*!0#/N!%*#F.*#(! 0*&+)#(EX!"'!'%(!N&$#/E$/5&$!+(-(+O!123!&E!*D+(!'/!5(#0/#N!(6FI'/I(6F!$%($ME)NN&64!'%#/)4%/)'!*++!$/6'#/++(#ID*E(F! $*$%(!$/N5/6(6'E!*++!'%(!.*J!F/.6!'/!'%(!F&EM!+(-(+X!!;%&E!&E!D($*)E(!'%(!,#*$+(!123!3'/#*4(!"55+&*6$(!)E(E!6/! 7":G!$/6'#/++(#Ei#*'%(#!'%(!E'/#*4(!$/6'#/++(#dZFSEE!/5(#*'&64!EJE'(N!&'E(+0!#)6E!123!F*'*!5#/'($'&/6X!;%&E!5#/-& checksums F(E!'%(! 0&+(!EJE'(N!0)++!(6FI'/I(6F!$/6'#/+!/0!F*'*!N/-(NN(6'!*6F!-&E&D&+&'J!/0!'%(!D+/$ME!E/!'%*'!0)++!*6F!&6'(4#*'(F!(6FI'/I(6F! $%($ME)NN&64!$*6!D(!5(#0/#N(FX!123!$%($ME)NN&64!&E!*!N/#(!*F-*6$(F!'J5(!/0!%&(#*#$%&$*+!$%($ME)NN&64! Unlike most-(#E)E!'%(!'#*F&'&/6*+!0+*'!$%($ME)NN&64!*55#/ other filesystems, each*$%X!;#*F&'&/6*+!$%($ME)NN&64!$*6!$%($M!'%(!&6'(4#&'J!/0!/6+J! data and metadata block of/6(! a ZFS D+/$M!&6!&E/+*'&/6!/0!/'%(#EO!N(*6&64!'%*'!N(F&*!!D&'!#/'!$*6!D(!E)$$(EE0)++J!E$#((6(FO!D)'!/'%(#!'J5(E!/0!F*'*! filesystem$/##)5'&/6!*$#/EE!'%(!:b,!5*'%!$*66/'!D(!&F(6'&0 has a SHA-256 checksum0&(FX!!123!$%($ME)NN&64!)E(E!*!H(#M+(!'#((O!.%(#(DJ!F*'*!D+ stored in the pointer to the/ block$ME! , not in the block*#(!F&E'&6$'!0#/N!*FF#(EE!D+/$M!$%($ME)NE!*6F! itself, so less subject'%(!(6'&#(!:b,!5*'%!$*6!D(!5#/'($'(F!0#/N!(6F!'/!(6FX! to corruption. ! [From Architectural Overview of the Oracle ZFS Storage Appliance] 2&4)#(!kc!;%(!123!*55#/*$%!'/!$%($ME)NE!$*6!F('($'!N/#(!'J5(E!/0!(##/#E!'%*6!'%(!'#*F&'&/6*+!*55#/*$%X! Checksums! on new blocks are recalculated, not copied, and errors can be "6/'%(#!*F-*6'*4(!/0!123!$%($ME)NN&64!&E!'%*'!&'!(6*D+(E!*!E(+0I%(*+&64!*#$%&'($')#(X!:6!E/N(!'#*F&'&/6*+!$%($ME)N! corrected*55#/*$%(EO!.%(#(-(#!F*'*!D+/$ME!4('!#(5+&$*' if there is sufficient redundancy(F!0#/N!/6(!+/$*'&/6!'/!*6/'%(#!'%(#(!&E!*6!/55/#')6&'J!'/!5#/5 (mirror or RAID-Zn replication).*4*'(! Nelson H. F. BeebeF*'*!$/##)5'&/6X!;%&E!&E!D($*)E(O!.&'%!'#*F&'&/6 and Pieter J. Bowman *+!$%($ME)N!*55#/*$%(EO!'%(!6(.(E'!F*'*!D+/$M!E&N5+J!4('E!Why ZFS? 10 November 2016 10 / 26 #(5+&$*'(FX!@&'%!123!$%($ME)NEO!(*$%!D+/$M!#((5+&$*!5*&#!%*E!*!$%($ME)N!$*+$)+*'(F!&6F(5(6F(6'+JX!:0!/6(!&E!0/)6F! '/!D(!$/##)5'(FO!'%(!%(*+'%J!D+/$M!&E!'%(6!)E(F!*E!*!#(0(#(6$(!'/!#(5*&#!'%(!)6%(*+'%J!D+/$MX! ! ! PT!!W!!!"789:;<8;=7">!,?<7?:<@!,2!;9<!,7"8><!123!3;,7"A<!"BB>:"C8<! ZFS snapshots fast: one or two seconds, independent of filesystem size unlimited number of snapshots snapshots are read-only snapshots are user visible [e.g., /.zfs/snapshot/auto-2016-10-11/home/jones/mail] /.zfs normally hidden from directory listing commands [management configurable] disk blocks captured in a snapshot are in use until snapshot is destroyed removing recent large files on a disk-full condition may free no space at all: instead, need to remove oldest snapshots a snapshot can be cloned to create a new writable filesystem Nelson H.
Load more

Recommended publications
  • Copy on Write Based File Systems Performance Analysis and Implementation
    Copy On Write Based File Systems Performance Analysis And Implementation Sakis Kasampalis Kongens Lyngby 2010 IMM-MSC-2010-63 Technical University of Denmark Department Of Informatics Building 321, DK-2800 Kongens Lyngby, Denmark Phone +45 45253351, Fax +45 45882673 [email protected] www.imm.dtu.dk Abstract In this work I am focusing on Copy On Write based file systems. Copy On Write is used on modern file systems for providing (1) metadata and data consistency using transactional semantics, (2) cheap and instant backups using snapshots and clones. This thesis is divided into two main parts. The first part focuses on the design and performance of Copy On Write based file systems. Recent efforts aiming at creating a Copy On Write based file system are ZFS, Btrfs, ext3cow, Hammer, and LLFS. My work focuses only on ZFS and Btrfs, since they support the most advanced features. The main goals of ZFS and Btrfs are to offer a scalable, fault tolerant, and easy to administrate file system. I evaluate the performance and scalability of ZFS and Btrfs. The evaluation includes studying their design and testing their performance and scalability against a set of recommended file system benchmarks. Most computers are already based on multi-core and multiple processor architec- tures. Because of that, the need for using concurrent programming models has increased. Transactions can be very helpful for supporting concurrent program- ming models, which ensure that system updates are consistent. Unfortunately, the majority of operating systems and file systems either do not support trans- actions at all, or they simply do not expose them to the users.
    [Show full text]
  • PDF, 32 Pages
    Helge Meinhard / CERN V2.0 30 October 2015 HEPiX Fall 2015 at Brookhaven National Lab After 2004, the lab, located on Long Island in the State of New York, U.S.A., was host to a HEPiX workshop again. Ac- cess to the site was considerably easier for the registered participants than 11 years ago. The meeting took place in a very nice and comfortable seminar room well adapted to the size and style of meeting such as HEPiX. It was equipped with advanced (sometimes too advanced for the session chairs to master!) AV equipment and power sockets at each seat. Wireless networking worked flawlessly and with good bandwidth. The welcome reception on Monday at Wading River at the Long Island sound and the workshop dinner on Wednesday at the ocean coast in Patchogue showed more of the beauty of the rather natural region around the lab. For those interested, the hosts offered tours of the BNL RACF data centre as well as of the STAR and PHENIX experiments at RHIC. The meeting ran very smoothly thanks to an efficient and experienced team of local organisers headed by Tony Wong, who as North-American HEPiX co-chair also co-ordinated the workshop programme. Monday 12 October 2015 Welcome (Michael Ernst / BNL) On behalf of the lab, Michael welcomed the participants, expressing his gratitude to the audience to have accepted BNL's invitation. He emphasised the importance of computing for high-energy and nuclear physics. He then intro- duced the lab focusing on physics, chemistry, biology, material science etc. The total head count of BNL-paid people is close to 3'000.
    [Show full text]
  • Proceedings of the Bsdcon 2002 Conference
    USENIX Association Proceedings of the BSDCon 2002 Conference San Francisco, California, USA February 11-14, 2002 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2002 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Rethinking /devand devices in the UNIX kernel Poul-Henning Kamp <[email protected]> The FreeBSD Project Abstract An outstanding novelty in UNIX at its introduction was the notion of ‘‘a file is a file is a file and evenadevice is a file.’’ Going from ‘‘hardware only changes when the DEC Field engineer is here’’to‘‘my toaster has USB’’has put serious strain on the rather crude implementation of the ‘‘devices as files’’concept, an implementation which has survivedpractically unchanged for 30 years in most UNIX variants. Starting from a high-levelviewofdevices and the semantics that have grown around them overthe years, this paper takes the audience on a grand tour of the redesigned FreeBSD device-I/O system, to convey anoverviewofhow itall fits together,and to explain whythings ended up as theydid, howtouse the newfeatures and in particular hownot to. 1. Introduction tax and meaning, so that a program expecting a file name as a parameter can be passed a device name; There are really only twofundamental ways to concep- finally,special files are subject to the same protec- tualise I/O devices in an operating system: The usual tion mechanism as regular files.
    [Show full text]
  • La Sécurité Informatique Edition Livres Pour Tous (
    La sécurité informatique Edition Livres pour tous (www.livrespourtous.com) PDF générés en utilisant l’atelier en source ouvert « mwlib ». Voir http://code.pediapress.com/ pour plus d’informations. PDF generated at: Sat, 13 Jul 2013 18:26:11 UTC Contenus Articles 1-Principes généraux 1 Sécurité de l'information 1 Sécurité des systèmes d'information 2 Insécurité du système d'information 12 Politique de sécurité du système d'information 17 Vulnérabilité (informatique) 21 Identité numérique (Internet) 24 2-Attaque, fraude, analyse et cryptanalyse 31 2.1-Application 32 Exploit (informatique) 32 Dépassement de tampon 34 Rétroingénierie 40 Shellcode 44 2.2-Réseau 47 Attaque de l'homme du milieu 47 Attaque de Mitnick 50 Attaque par rebond 54 Balayage de port 55 Attaque par déni de service 57 Empoisonnement du cache DNS 66 Pharming 69 Prise d'empreinte de la pile TCP/IP 70 Usurpation d'adresse IP 71 Wardriving 73 2.3-Système 74 Écran bleu de la mort 74 Fork bomb 82 2.4-Mot de passe 85 Attaque par dictionnaire 85 Attaque par force brute 87 2.5-Site web 90 Cross-site scripting 90 Défacement 93 2.6-Spam/Fishing 95 Bombardement Google 95 Fraude 4-1-9 99 Hameçonnage 102 2.7-Cloud Computing 106 Sécurité du cloud 106 3-Logiciel malveillant 114 Logiciel malveillant 114 Virus informatique 120 Ver informatique 125 Cheval de Troie (informatique) 129 Hacktool 131 Logiciel espion 132 Rootkit 134 Porte dérobée 145 Composeur (logiciel) 149 Charge utile 150 Fichier de test Eicar 151 Virus de boot 152 4-Concepts et mécanismes de sécurité 153 Authentification forte
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Advanced Services for Oracle Hierarchical Storage Manager
    ORACLE DATA SHEET Advanced Services for Oracle Hierarchical Storage Manager The complex challenge of managing the data lifecycle is simply about putting the right data, on the right storage tier, at the right time. Oracle Hierarchical Storage Manager software enables you to reduce the cost of managing data and storing vast data repositories by providing a powerful, easily managed, cost-effective way to access, retain, and protect data over its entire lifecycle. However, your organization must ensure that your archive software is configured and optimized to meet strategic business needs and regulatory demands. Oracle Advanced Services for Oracle Hierarchical Storage Manager delivers the configuration expertise, focused reviews, and proactive guidance to help optimize the effectiveness of your solution–all delivered by Oracle Advanced Support Engineers. KEY BENEFITS Simplify Storage Management • Preproduction Readiness Services including critical patches and Putting the right information on the appropriate tier can reduce storage costs and updates, using proven methodologies maximize return on investment (ROI) over time. Oracle Hierarchical Storage Manager and recommended practices software actively manages data between storage tiers to let companies exploit the • Production Optimization Services substantial acquisition and operational cost differences between high-end disk drives, including configuration reviews and SATA drives, and tape devices. Oracle Hierarchical Storage Manager software provides performance reviews to analyze existing
    [Show full text]
  • 11.7 the Windows 2000 File System
    830 CASE STUDY 2: WINDOWS 2000 CHAP. 11 11.7 THE WINDOWS 2000 FILE SYSTEM Windows 2000 supports several file systems, the most important of which are FAT-16, FAT-32, and NTFS (NT File System). FAT-16 is the old MS-DOS file system. It uses 16-bit disk addresses, which limits it to disk partitions no larger than 2 GB. FAT-32 uses 32-bit disk addresses and supports disk partitions up to 2 TB. NTFS is a new file system developed specifically for Windows NT and car- ried over to Windows 2000. It uses 64-bit disk addresses and can (theoretically) support disk partitions up to 264 bytes, although other considerations limit it to smaller sizes. Windows 2000 also supports read-only file systems for CD-ROMs and DVDs. It is possible (even common) to have the same running system have access to multiple file system types available at the same time. In this chapter we will treat the NTFS file system because it is a modern file system unencumbered by the need to be fully compatible with the MS-DOS file system, which was based on the CP/M file system designed for 8-inch floppy disks more than 20 years ago. Times have changed and 8-inch floppy disks are not quite state of the art any more. Neither are their file systems. Also, NTFS differs both in user interface and implementation in a number of ways from the UNIX file system, which makes it a good second example to study. NTFS is a large and complex system and space limitations prevent us from covering all of its features, but the material presented below should give a reasonable impression of it.
    [Show full text]
  • Solaris 10 End of Life
    Solaris 10 end of life Continue Oracle Solaris 10 has had an amazing OS update, including ground features such as zones (Solaris containers), FSS, Services, Dynamic Tracking (against live production operating systems without impact), and logical domains. These features have been imitated in the market (imitation is the best form of flattery!) like all good things, they have to come to an end. Sun Microsystems was acquired by Oracle and eventually, the largest OS known to the industry, needs to be updated. Oracle has set a retirement date of January 2021. Oracle indicated that Solaris 10 systems would need to raise support costs. Oracle has never provided migratory tools to facilitate migration from Solaris 10 to Solaris 11, so migration to Solaris has been slow. In September 2019, Oracle decided that extended support for Solaris 10 without an additional financial penalty would be delayed until 2024! Well its March 1 is just a reminder that Oracle Solaris 10 is getting the end of life regarding support if you accept extended support from Oracle. Combined with the fact gdpR should take effect on May 25, 2018 you want to make sure that you are either upgraded to Solaris 11.3 or have taken extended support to obtain any patches for security issues. For more information on tanningix releases and support dates of old and new follow this link ×Sestive to abort the Unix Error Operating System originally developed by Sun Microsystems SolarisDeveloperSun Microsystems (acquired by Oracle Corporation in 2009)Written inC, C'OSUnixWorking StateCurrentSource ModelMixedInitial release1992; 28 years ago (1992-06)Last release11.4 / August 28, 2018; 2 years ago (2018-08-28)Marketing targetServer, PlatformsCurrent: SPARC, x86-64 Former: IA-32, PowerPCKernel typeMonolithic with dynamically downloadable modulesDefault user interface GNOME-2-LicenseVariousOfficial websitewww.oracle.com/solaris Solaris is the own operating system Of Unix, originally developed by Sunsystems.
    [Show full text]
  • Github: a Case Study of Linux/BSD Perceptions from Microsoft's
    1 FLOSS != GitHub: A Case Study of Linux/BSD Perceptions from Microsoft’s Acquisition of GitHub Raula Gaikovina Kula∗, Hideki Hata∗, Kenichi Matsumoto∗ ∗Nara Institute of Science and Technology, Japan {raula-k, hata, matumoto}@is.naist.jp Abstract—In 2018, the software industry giants Microsoft made has had its share of disagreements with Microsoft [6], [7], a move into the Open Source world by completing the acquisition [8], [9], the only reported negative opinion of free software of mega Open Source platform, GitHub. This acquisition was not community has different attitudes towards GitHub is the idea without controversy, as it is well-known that the free software communities includes not only the ability to use software freely, of ‘forking’ so far, as it it is considered as a danger to FLOSS but also the libre nature in Open Source Software. In this study, development [10]. our aim is to explore these perceptions in FLOSS developers. We In this paper, we report on how external events such as conducted a survey that covered traditional FLOSS source Linux, acquisition of the open source platform by a closed source and BSD communities and received 246 developer responses. organization triggers a FLOSS developers such the Linux/ The results of the survey confirm that the free community did trigger some communities to move away from GitHub and raised BSD Free Software communities. discussions into free and open software on the GitHub platform. The study reminds us that although GitHub is influential and II. TARGET SUBJECTS AND SURVEY DESIGN trendy, it does not representative all FLOSS communities.
    [Show full text]
  • Installing Oracle Goldengate
    Oracle® Fusion Middleware Installing Oracle GoldenGate 12c (12.3.0.1) E85215-07 November 2018 Oracle Fusion Middleware Installing Oracle GoldenGate, 12c (12.3.0.1) E85215-07 Copyright © 2017, 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]
  • Adventures with Illumos
    > Adventures with illumos Peter Tribble Theoretical Astrophysicist Sysadmin (DBA) Technology Tinkerer > Introduction ● Long-time systems administrator ● Many years pointing out bugs in Solaris ● Invited onto beta programs ● Then the OpenSolaris project ● Voted onto OpenSolaris Governing Board ● Along came Oracle... ● illumos emerged from the ashes > key strengths ● ZFS – reliable and easy to manage ● Dtrace – extreme observability ● Zones – lightweight virtualization ● Standards – pretty strict ● Compatibility – decades of heritage ● “Solarishness” > Distributions ● Solaris 11 (OpenSolaris based) ● OpenIndiana – OpenSolaris ● OmniOS – server focus ● SmartOS – Joyent's cloud ● Delphix/Nexenta/+ – storage focus ● Tribblix – one of the small fry ● Quite a few others > Solaris 11 ● IPS packaging ● SPARC and x86 – No 32-bit x86 – No older SPARC (eg Vxxx or SunBlades) ● Unique/key features – Kernel Zones – Encrypted ZFS – VM2 > OpenIndiana ● Direct continuation of OpenSolaris – Warts and all ● IPS packaging ● X86 only (32 and 64 bit) ● General purpose ● JDS desktop ● Generally rather stale > OmniOS ● X86 only ● IPS packaging ● Server focus ● Supported commercial offering ● Stable components can be out of date > XStreamOS ● Modern variant of OpenIndiana ● X86 only ● IPS packaging ● Modern lightweight desktop options ● Extra applications – LibreOffice > SmartOS ● Hypervisor, not general purpose ● 64-bit x86 only ● Basis of Joyent cloud ● No inbuilt packaging, pkgsrc for applications ● Added extra features – KVM guests – Lots of zone features –
    [Show full text]
  • ZFS 2018 and Onward
    SEE TEXT ONLY 2018 and Onward BY ALLAN JUDE 2018 is going to be a big year for ZFS RAID-Z Expansion not only FreeBSD, but for OpenZFS • 2018Q4 as well. OpenZFS is the collaboration of developers from IllumOS, FreeBSD, The ability to add an additional disk to an existing RAID-Z VDEV to grow its size with- Linux, Mac OS X, many industry ven- out changing its redundancy level. For dors, and a number of other projects example, a RAID-Z2 consisting of 6 disks to maintain and advance the open- could be expanded to contain 7 disks, source version of Sun’s ZFS filesystem. increasing the available space. This is accomplished by reflowing the data across Improved Pool Import the disks, so as to not change an individual • 2018Q1 block’s offset from the start of the VDEV. The new disk will appear as a new column on the A new patch set changes the way pools are right, and the data will be relocated to main- imported, such that they depend less on con- tain the offset within the VDEV. Similar to figuration data from the system. Instead, the reflowing a paragraph by making it wider, possibly outdated configuration from the sys- without changing the order of the words. In tem is used to find the pool, and partially open the end this means all of the new space shows it read-only. Then the correct on-disk configura- up at the end of the disk, without any frag- tion is loaded. This reduces the number of mentation.
    [Show full text]