DOCSLIB.ORG

Red Hat Enterprise Linux 7 7.0 Release Notes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Red Hat Enterprise Linux 7 7.0 Release Notes Red Hat Enterprise Linux 7 7.0 Release Notes Release Notes for Red Hat Enterprise Linux 7 Red Hat Engineering Content Services Red Hat Enterprise Linux 7 7.0 Release Notes Release Notes for Red Hat Enterprise Linux 7 Red Hat Engineering Content Services Legal Notice Copyright © 2014 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract The Release Notes documents the major features and enhancements implemented in Red Hat Enterprise Linux 7 and the known issues in this 7.0 release. For detailed information regarding the changes between Red Hat Enterprise Linux 6 and 7, consult the Migration Planning Guide. Acknowledgements Red Hat Global Support Services would like to recognize Sterling Alexander and Michael Everette for their outstanding contributions in testing Red Hat Enterprise Linux 7. T able of Cont ent s Table of Contents .I n. t. r.o .d . u. c. t. i.o .n . 5. ⁠.P .a .r t. .I .. N. .e .w . F. e. a. t. u. r. e. s. 6. ⁠.C .h .a .p . t.e .r . 1. .. A. r. c. h. i.t .e .c .t u. .r e. s. 7. ⁠.C .h .a .p . t.e .r . 2. .. I.n .s .t .a .l l.a .t .i o. n. .a .n . d. .B . o. o. t. i.n .g . 8. ⁠2.1. Installer 8 ⁠2.2. Bo o t Lo ad er 11 ⁠.C .h .a .p . t.e .r . 3. .. S. t. o. r.a .g . e. 1. 3. ⁠LIO kernel Targ et Sub system 13 ⁠LVM Cache 13 ⁠Sto rag e Array Manag ement with lib Sto rag eMg mt API 13 ⁠Sup p o rt fo r LSI Syncro 13 ⁠LVM Ap p licatio n Pro g ramming Interface 13 ⁠DIF/DIX Sup p o rt 14 ⁠Sup p o rt o f Parallel NFS 14 ⁠.C .h .a .p . t.e .r . 4. .. F. i.l e. .S .y .s .t .e .m . s. 1. 5. ⁠Sup p o rt o f XFS File System 15 ⁠Sup p o rt o f Btrfs File System 15 ⁠Fast Blo ck Devices Caching Slo wer Blo ck Devices 15 ⁠.C .h .a .p . t.e .r . 5. .. K. e. r.n . e. l. 1. 6. ⁠Dynamic kernel Patching 16 ⁠Sup p o rt fo r Larg e crashkernel Sizes 16 ⁠Crashkernel With Mo re Than 1 CPU 16 ⁠Swap Memo ry Co mp ressio n 16 ⁠NUMA-Aware Sched uling and Memo ry Allo catio n 16 ⁠APIC Virtualizatio n 16 ⁠vmcp Built in the Kernel 16 ⁠Hard ware Erro r Rep o rting Mechanism 16 ⁠Full DynTick Sup p o rt 17 ⁠Blacklisting kernel Mo d ules 17 ⁠d m-era Targ et 17 ⁠AMD Micro co d e and AMD Op tero n Sup p o rt 17 ⁠Availab le Memo ry fo r /p ro c/meminfo 18 ⁠Op en vSwitch Kernel Mo d ule 18 ⁠5.1. IBM System z Features and Techno lo g y Previews 18 ⁠.C .h .a .p . t.e .r . 6. .. V. i.r .t u. .a .l i.z .a .t i.o . n. 2. 0. ⁠6 .1. Kernel-Based Virtualizatio n 20 ⁠6 .2. Xen 24 ⁠6 .3. Hyp er-V 24 ⁠6 .4. VMware 24 ⁠.C .h .a .p . t.e .r . 7. .. L. i.n .u . x. .C .o .n . t.a .i n. .e .r s. .w . i.t h. D. o. .c .k e. r. .F .o .r m. .a .t . 2. 6. ⁠7.1. Co mp o nents o f Do cker Co ntainers 26 ⁠7.2. Ad vantag es o f Using Do cker 27 ⁠7.3. Co mp ariso n with Virtual Machines 27 ⁠7.4. Using Do cker o n Red Hat Enterp rise Linux 7 28 ⁠.C .h .a .p . t.e .r . 8. .. S. y. s. t. e. m. a. n. d. S. e. r.v .i c. e. s. 2. 9. ⁠systemd 29 1 Red Hat Ent erprise Linux 7 7 .0 Release Not es ⁠systemd 29 ⁠.C .h .a .p . t.e .r . 9. .. C. l.u . s. t.e .r .i n. g. 3. 0. ..
Load more

Recommended publications
  • Red Hat Enterprise Linux 7 7.1 Release Notes
    Red Hat Enterprise Linux 7 7.1 Release Notes Release Notes for Red Hat Enterprise Linux 7 Red Hat Customer Content Services Red Hat Enterprise Linux 7 7.1 Release Notes Release Notes for Red Hat Enterprise Linux 7 Red Hat Customer Content Services Legal Notice Copyright © 2015 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Speeding up Linux Disk Encryption Ignat Korchagin @Ignatkn $ Whoami
    Speeding Up Linux Disk Encryption Ignat Korchagin @ignatkn $ whoami ● Performance and security at Cloudflare ● Passionate about security and crypto ● Enjoy low level programming @ignatkn Encrypting data at rest The storage stack applications @ignatkn The storage stack applications filesystems @ignatkn The storage stack applications filesystems block subsystem @ignatkn The storage stack applications filesystems block subsystem storage hardware @ignatkn Encryption at rest layers applications filesystems block subsystem SED, OPAL storage hardware @ignatkn Encryption at rest layers applications filesystems LUKS/dm-crypt, BitLocker, FileVault block subsystem SED, OPAL storage hardware @ignatkn Encryption at rest layers applications ecryptfs, ext4 encryption or fscrypt filesystems LUKS/dm-crypt, BitLocker, FileVault block subsystem SED, OPAL storage hardware @ignatkn Encryption at rest layers DBMS, PGP, OpenSSL, Themis applications ecryptfs, ext4 encryption or fscrypt filesystems LUKS/dm-crypt, BitLocker, FileVault block subsystem SED, OPAL storage hardware @ignatkn Storage hardware encryption Pros: ● it’s there ● little configuration needed ● fully transparent to applications ● usually faster than other layers @ignatkn Storage hardware encryption Pros: ● it’s there ● little configuration needed ● fully transparent to applications ● usually faster than other layers Cons: ● no visibility into the implementation ● no auditability ● sometimes poor security https://support.microsoft.com/en-us/help/4516071/windows-10-update-kb4516071 @ignatkn Block
    [Show full text]
  • DM-Relay - Safe Laptop Mode Via Linux Device Mapper
    ' $ DM-Relay - Safe Laptop Mode via Linux Device Mapper Study Thesis by cand. inform. Fabian Franz at the Faculty of Informatics Supervisor: Prof. Dr. Frank Bellosa Supervising Research Assistant: Dipl.-Inform. Konrad Miller Day of completion: 04/05/2010 &KIT – Universitat¨ des Landes Baden-Wurttemberg¨ und nationales Forschungszentrum in der Helmholtz-Gemeinschaft www.kit.edu % I hereby declare that this thesis is my own original work which I created without illegitimate help by others, that I have not used any other sources or resources than the ones indicated and that due acknowledgment is given where reference is made to the work of others. Karlsruhe, April 5th, 2010 Contents Deutsche Zusammenfassung xi 1 Introduction 1 1.1 Problem Definition . .1 1.2 Objectives . .1 1.3 Methodology . .1 1.4 Contribution . .2 1.5 Thesis Outline . .2 2 Background 3 2.1 Problems of Disk Power Management . .3 2.2 State of the Art . .4 2.3 Summary of this chapter . .8 3 Analysis 9 3.1 Pro and Contra . .9 3.2 A new approach . 13 3.3 Analysis of Proposal . 15 3.4 Summary of this chapter . 17 4 Design 19 4.1 Common problems . 19 4.2 System-Design . 21 4.3 Summary of this chapter . 21 5 Implementation of a dm-module for the Linux kernel 23 5.1 System-Architecture . 24 5.2 Log suitable for Flash-Storage . 28 5.3 Using dm-relay in practice . 31 5.4 Summary of this chapter . 31 vi Contents 6 Evaluation 33 6.1 Methodology . 33 6.2 Benchmarking setup .
    [Show full text]
  • A Hybrid Swapping Scheme Based on Per-Process Reclaim for Performance Improvement of Android Smartphones (August 2018)
    Received August 19, 2018, accepted September 14, 2018, date of publication October 1, 2018, date of current version October 25, 2018. Digital Object Identifier 10.1109/ACCESS.2018.2872794 A Hybrid Swapping Scheme Based On Per-Process Reclaim for Performance Improvement of Android Smartphones (August 2018) JUNYEONG HAN 1, SUNGEUN KIM1, SUNGYOUNG LEE1, JAEHWAN LEE2, AND SUNG JO KIM2 1LG Electronics, Seoul 07336, South Korea 2School of Software, Chung-Ang University, Seoul 06974, South Korea Corresponding author: Sung Jo Kim ([email protected]) This work was supported in part by the Basic Science Research Program through the National Research Foundation of Korea (NRF) funded by the Ministry of Education under Grant 2016R1D1A1B03931004 and in part by the Chung-Ang University Research Scholarship Grants in 2015. ABSTRACT As a way to increase the actual main memory capacity of Android smartphones, most of them make use of zRAM swapping, but it has limitation in increasing its capacity since it utilizes main memory. Unfortunately, they cannot use secondary storage as a swap space due to the long response time and wear-out problem. In this paper, we propose a hybrid swapping scheme based on per-process reclaim that supports both secondary-storage swapping and zRAM swapping. It attempts to swap out all the pages in the working set of a process to a zRAM swap space rather than killing the process selected by a low-memory killer, and to swap out the least recently used pages into a secondary storage swap space. The main reason being is that frequently swap- in/out pages use the zRAM swap space while less frequently swap-in/out pages use the secondary storage swap space, in order to reduce the page operation cost.
    [Show full text]
  • Sbadmin Device-Mapper Multipath Devices
    DM-Multipath Guide Version 8.2 SBAdmin and DM-Multipath Guide The purpose of this guide is to provide the steps necessary to use SBAdmin in an environment where SAN storage is used in conjunction with device-mapper multipath devices. When a system is using dm-multipath devices, there are several considerations that need to be addressed. The device naming, tools available, and device modules loaded become critical issues in discovery of devices and recreation of those devices upon restore. The information in this guide should provide the necessary information to create backups from systems using dm-multipath devices or for users who want to migrate a system backup to multipath devices. This guide is not intended to assist users in the initial setup of dm-multipath devices. For information on initially setting up dm-multipath devices, contact your Linux OS support vendors directly. Requirements for DM-Multipath support Software requirements Support for dm-multipath devices has been available to Linux users for years, however, how the devices are created and supported by distributions has changed greatly over time as the technology matures. Below is the minimal level of the tools and file sets that SBAdmin has tested and will support. dm-multipath-tools version 0.4.5 (also known as device-mapper-multipath) device-mapper version 1.02 udev version 039-10 Device detection requirements Device naming If you plan on creating backups from a system using dm-multipath devices, the SBAdmin software must be able to recognize the devices by name prior to creating the backup. Multipath devices can be named several different ways such as by the World Wide Identifier (WWID), dm-[0-9], mpath[a-z], and mpath[0-9].
    [Show full text]
  • I.MX Encrypted Storage Using CAAM Secure Keys Rev
    AN12714 i.MX Encrypted Storage Using CAAM Secure Keys Rev. 1 — 11/2020 Application Note Contents 1 Preface 1 Preface............................................1 Devices often contain highly sensitive information which is consistently at risk 1.1 Intended audience and scope......1 1.2 References...................................1 to get physically lost or stolen. Setting user passwords does not guarantee data 2 Overview......................................... 1 protection against unauthorized access. The attackers can simply bypass the 2.1 DM-Crypt......................................1 software system of a device and access the data storage directly. Only the 2.2 DM-Crypt accelerated by CAAM use of encryption can guarantee data confidentiality in the case where storage .....................................................2 media is directly accessed. 2.3 DM-Crypt using CAAM's Secure Key...............................................3 This document provides steps to run a transparent storage encryption at block 3 Hands-On........................................4 level using DM-Crypt taking advantage of the secure key feature provided 3.1 Installation....................................4 by i.MXs Cryptographic Accelerator and Assurance Module (CAAM). The 3.2 Usage...........................................6 document applies to all i.MX SoCs having CAAM module. The feature is not 3.3 Performance................................ 9 available on i.MX SoCs with DCP. 4 Revision History............................ 10 5 Appendix A. Configuration...........
    [Show full text]
  • Think ALL Distros Offer the Best Linux Devsecops Environment?
    Marc Staimer, Dragon Slayor Consulting WHITE PAPER Think All Distros Offer the Best Linux DevSecOps What You’re Not Being Told About Environment? Database as a Service (DBaaS) Think Again! WHITE PAPER • Think Again! Think All Distros Provide the Best Linux DevSecOps Environment? Think Again! Introduction DevOps is changing. Developing code with after the fact bolt-on security is dangerously flawed. When that bolt-on fails to correct exploitable code vulnerabilities, it puts the entire organization at risk. Security has been generally an afterthought for many doing DevOps. It was often assumed the IT organization’s systemic multiple layers of security measures and appliances would protect any new code from malware or breaches. And besides, developing code with security built in, adds tasks and steps to development and testing time. More tasks and steps delay time-to-market. Multi-tenant clouds have radically changed the market. Any vulnerability in a world with increasing cyber-attacks, can put millions of user’s data at risk. Those legacy DevOps attitudes are unsound. They are potentially quite costly in the current environment. Consider that nearly every developed and most developing countries have enacted laws and regulation protecting personally identifiable information or PII1. PII is incredibly valuable to cybercriminals. Stealing PII enables them to commit many cybercrimes including the cybertheft of identities, finances, intellectual property, admin privileges, and much more. PII can also be sold on the web. Those PII laws and regulations are meant to force IT organizations to protect PII. Non-compliance of these laws and regulations often carry punitive financial penalties.
    [Show full text]
  • Instant OS Updates Via Userspace Checkpoint-And
    Instant OS Updates via Userspace Checkpoint-and-Restart Sanidhya Kashyap, Changwoo Min, Byoungyoung Lee, and Taesoo Kim, Georgia Institute of Technology; Pavel Emelyanov, CRIU and Odin, Inc. https://www.usenix.org/conference/atc16/technical-sessions/presentation/kashyap This paper is included in the Proceedings of the 2016 USENIX Annual Technical Conference (USENIX ATC ’16). June 22–24, 2016 • Denver, CO, USA 978-1-931971-30-0 Open access to the Proceedings of the 2016 USENIX Annual Technical Conference (USENIX ATC ’16) is sponsored by USENIX. Instant OS Updates via Userspace Checkpoint-and-Restart Sanidhya Kashyap Changwoo Min Byoungyoung Lee Taesoo Kim Pavel Emelyanov† Georgia Institute of Technology †CRIU & Odin, Inc. # errors # lines Abstract 50 1000K 40 100K In recent years, operating systems have become increas- 10K 30 1K 20 ingly complex and thus more prone to security and per- 100 formance issues. Accordingly, system updates to address 10 10 these issues have become more frequently available and 0 1 increasingly important. To complete such updates, users 3.13.0-x 3.16.0-x 3.19.0-x May 2014 must reboot their systems, resulting in unavoidable down- build/diff errors #layout errors Jun 2015 time and further loss of the states of running applications. #static local errors #num lines++ We present KUP, a practical OS update mechanism that Figure 1: Limitation of dynamic kernel hot-patching using employs a userspace checkpoint-and-restart mechanism, kpatch. Only two successful updates (3.13.0.32 34 and → which uses an optimized data structure for checkpoint- 3.19.0.20 21) out of 23 Ubuntu kernel package releases.
    [Show full text]
  • Device Mapper (Kernel Part of LVM2 Volume Management) Milan Brož [email protected] Device Mapper
    Device mapper (kernel part of LVM2 volume management) Milan Brož [email protected] Device mapper ... modular Linux 2.6 kernel driver . framework for constructing new block devices and mapping them to existing block devices . managed through API (IOCTL interface) . libdevmapper, dmsetup command utility DM knows nothing about ● LVM (logical volumes, volume groups) ► managed by userspace tools (LVM2, EVMS, ...) ● partitions, filesystems ► managed by userspace tools (fdisk, mkfs, mount, ...) 2 Device mapper – mapped device access application write() USERSPACE VFS filesystem ... /dev/mapper/<dev> DEVICE Map IO BLOCK MAPPER LAYER [ MAPPING TABLE ] LOW LEVEL DRIVERS PHYSICAL DEVICES /dev/sda ... EXAMPLE KERNEL 3 Device mapper – control interface application LVM2 application DM library (libdevmapper) USERSPACE IOCTL INTERFACE MAPPING DEVICE MAPPER TABLES DM TARGETS KERNEL 4 Device mapper - TARGETS . linear – maps continuous range of another block device . striped (~RAID0) – striping across devices . mirror (~RAID1) – mirroring devices . crypt – encrypt data using CryptoAPI . snapshot – online snapshots of block device . multipath – access to multipath devices (misc. hw handlers) . zero,error,delay – test and special targets . truecrypt ... raid45 (~RAID4,5) – raid (with dedicated) parity . loop – stack device over another or over file . throttle, rwsplit, flakey – test targets 5 Device mapper – applications lvm2*[.rpm] dmraid*[.rpm] cryptsetup*[.rpm] ... device-mapper*[.rpm] LVM2 EVMS DMRAID cryptsetup ... dmsetup libdevmapper USERSPACE /dev/mapper/control KERNEL DEVICE MAPPER DM & LVM2 / DevConf 2007 6 Simulate disk fail – 100MB disk with bad 9th sector Create new disk and map 9th sector to error target dmsetup create bad_disk 0 8 linear /dev/sdb1 0 8 1 error 9 204791 linear /dev/sdb1 9 Set readahead to 0, check block device size blockdev --setra 0 /dev/mapper/bad_disk blockdev --getsz /dev/mapper/bad_disk DD should fail on 9th sector..
    [Show full text]
  • Dm-Cache.Pdf
    DM-Cache Marc Skinner Principal Solutions Architect Twin Cities Users Group :: Q1/2016 Why Cache? ● Spinning disks are slow! ● Solid state disks (SSD) are fast!! ● Non-Volatile Memory Express (NVMe) devices are insane!!! Why not? ● Hybrid drives make 5900rpm drives act like 7200rpm drives with very small on board SSD cache ● Hmm, talk to FAST and move to SLOW? FAST SLOW Linux Caching Options ● DM-Cache ● Oldest and most stable. Developed in 2006 by IBM research group, and merged into Linux kernel tree in version 3.9. Uses the device-mapper framework to cache a slower device ● FlashCache ● Kernel module inspired by dm-cache and developed/maintained by Facebook. Also uses the device-mapper framework. ● EnhanceIO, RapidCache ● Both variations of FlashCache ● BCache ● Newest option and does not rely on device-mapper framework DM-Cache Modes ● write-through ● Red Hat default ● Write requests are not returned until the data reaches the origin and the cache device ● write-back ● Writes go only to the cache device ● pass-through ● Used to by pass the cache, used if cache is corrupt DM-Cache Setup ● Enable discards first # vi /etc/lvm/lvm.conf issue_discards = 1 # dracut -f # sync # reboot DM-Cache Setup ● Create PV, VG and LV with Cache # pvcreate /dev/md2 (raid 10 - 6 x 250gb SSD) # pvcreate /dev/md3 (raid 10 - 6 x 2tb SATA) # vgcreate vg_iscsi /dev/md3 /dev/md2 # lvcreate -l 100%FREE -n lv_sata vg_iscsi /dev/md3 # lvcreate -L 5G -n lv_cache_meta vg_iscsi /dev/md2 # lvcreate -L 650G -n lv_cache vg_iscsi /dev/md2 # lvconvert --type cache-pool
    [Show full text]
  • Red Hat Enterprise Linux 7 Kernel Administration Guide
    Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Last Updated: 2018-05-21 Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Marie Dolezelova Red Hat Customer Content Services [email protected] Mark Flitter Red Hat Customer Content Services Douglas Silas Red Hat Customer Content Services Eliska Slobodova Red Hat Customer Content Services Jaromir Hradilek Red Hat Customer Content Services Maxim Svistunov Red Hat Customer Content Services Robert Krátký Red Hat Customer Content Services Stephen Wadeley Red Hat Customer Content Services Florian Nadge Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. 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. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates.
    [Show full text]
  • Linux Multipathing
    Linux Multipathing Edward Goggin Alasdair Kergon Christophe Varoqui EMC Corporation Red Hat [email protected] [email protected] [email protected] David Olien OSDL [email protected] Abstract hosts, multipathing re-routes block io to an al- ternate path in the event of one or more path connectivity failures. Multipathing also trans- Linux multipathing provides io failover and parently shares io load across the multiple paths path load sharing for multipathed block de- to the same block device. vices. In this paper, we provide an overview of the current device mapper based multi- The history of Linux multipathing goes back pathing capability and describe Enterprise level at least 3 years and offers a variety of differ- requirements for future multipathing enhance- ent architectures. The multipathing personal- ments. We describe the interaction amongst ity of the multidisk driver first provided block kernel multipathing modules, user mode mul- device multipathing in the 2.4.17 kernel. The tipathing tools, hotplug, udev, and kpartx com- Qlogic FC HBA driver has provided multi- ponents when considering use cases. Use cases pathing across Qlogic FC initiators since 2002. include path and logical unit re-configuration, Storage system OEM vendors like IBM, Hi- partition management, and path failover for tachi, HP, Fujitsu, and EMC have provided both active-active and active-passive generic multipathing solutions for Linux for several storage systems. We also describe lessons years. Strictly software vendors like Veritas learned during testing the MD scheme on high- also provide Linux multipathing solutions. end storage. In this paper, we describe the current 2.6 Linux kernel multipathing solution built around the 1 Introduction kernel’s device mapper block io framework and consider possible enhancements.
    [Show full text]