The Great Migration Final
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
The Kernel Report
The kernel report (ELC 2012 edition) Jonathan Corbet LWN.net [email protected] The Plan Look at a year's worth of kernel work ...with an eye toward the future Starting off 2011 2.6.37 released - January 4, 2011 11,446 changes, 1,276 developers VFS scalability work (inode_lock removal) Block I/O bandwidth controller PPTP support Basic pNFS support Wakeup sources What have we done since then? Since 2.6.37: Five kernel releases have been made 59,000 changes have been merged 3069 developers have contributed to the kernel 416 companies have supported kernel development February As you can see in these posts, Ralink is sending patches for the upstream rt2x00 driver for their new chipsets, and not just dumping a huge, stand-alone tarball driver on the community, as they have done in the past. This shows a huge willingness to learn how to deal with the kernel community, and they should be strongly encouraged and praised for this major change in attitude. – Greg Kroah-Hartman, February 9 Employer contributions 2.6.38-3.2 Volunteers 13.9% Wolfson Micro 1.7% Red Hat 10.9% Samsung 1.6% Intel 7.3% Google 1.6% unknown 6.9% Oracle 1.5% Novell 4.0% Microsoft 1.4% IBM 3.6% AMD 1.3% TI 3.4% Freescale 1.3% Broadcom 3.1% Fujitsu 1.1% consultants 2.2% Atheros 1.1% Nokia 1.8% Wind River 1.0% Also in February Red Hat stops releasing individual kernel patches March 2.6.38 released – March 14, 2011 (9,577 changes from 1198 developers) Per-session group scheduling dcache scalability patch set Transmit packet steering Transparent huge pages Hierarchical block I/O bandwidth controller Somebody needs to get a grip in the ARM community. -
An Analysis of Data Corruption in the Storage Stack
An Analysis of Data Corruption in the Storage Stack Lakshmi N. Bairavasundaram∗, Garth R. Goodson†, Bianca Schroeder‡ Andrea C. Arpaci-Dusseau∗, Remzi H. Arpaci-Dusseau∗ ∗University of Wisconsin-Madison †Network Appliance, Inc. ‡University of Toronto {laksh, dusseau, remzi}@cs.wisc.edu, [email protected], [email protected] Abstract latent sector errors, within disk drives [18]. Latent sector errors are detected by a drive’s internal error-correcting An important threat to reliable storage of data is silent codes (ECC) and are reported to the storage system. data corruption. In order to develop suitable protection Less well-known, however, is that current hard drives mechanisms against data corruption, it is essential to un- and controllers consist of hundreds-of-thousandsof lines derstand its characteristics. In this paper, we present the of low-level firmware code. This firmware code, along first large-scale study of data corruption. We analyze cor- with higher-level system software, has the potential for ruption instances recorded in production storage systems harboring bugs that can cause a more insidious type of containing a total of 1.53 million disk drives, over a pe- disk error – silent data corruption, where the data is riod of 41 months. We study three classes of corruption: silently corrupted with no indication from the drive that checksum mismatches, identity discrepancies, and par- an error has occurred. ity inconsistencies. We focus on checksum mismatches since they occur the most. Silent data corruptionscould lead to data loss more of- We find more than 400,000 instances of checksum ten than latent sector errors, since, unlike latent sector er- mismatches over the 41-month period. -
Rootless Containers with Podman and Fuse-Overlayfs
CernVM Workshop 2019 (4th June 2019) Rootless containers with Podman and fuse-overlayfs Giuseppe Scrivano @gscrivano Introduction 2 Rootless Containers • “Rootless containers refers to the ability for an unprivileged user (i.e. non-root user) to create, run and otherwise manage containers.” (https://rootlesscontaine.rs/ ) • Not just about running the container payload as an unprivileged user • Container runtime runs also as an unprivileged user 3 Don’t confuse with... • sudo podman run --user foo – Executes the process in the container as non-root – Podman and the OCI runtime still running as root • USER instruction in Dockerfile – same as above – Notably you can’t RUN dnf install ... 4 Don’t confuse with... • podman run --uidmap – Execute containers as a non-root user, using user namespaces – Most similar to rootless containers, but still requires podman and runc to run as root 5 Motivation of Rootless Containers • To mitigate potential vulnerability of container runtimes • To allow users of shared machines (e.g. HPC) to run containers without the risk of breaking other users environments • To isolate nested containers 6 Caveat: Not a panacea • Although rootless containers could mitigate these vulnerabilities, it is not a panacea , especially it is powerless against kernel (and hardware) vulnerabilities – CVE 2013-1858, CVE-2015-1328, CVE-2018-18955 • Castle approach : it should be used in conjunction with other security layers such as seccomp and SELinux 7 Podman 8 Rootless Podman Podman is a daemon-less alternative to Docker • $ alias -
Dm-X: Protecting Volume-Level Integrity for Cloud Volumes and Local
dm-x: Protecting Volume-level Integrity for Cloud Volumes and Local Block Devices Anrin Chakraborti Bhushan Jain Jan Kasiak Stony Brook University Stony Brook University & Stony Brook University UNC, Chapel Hill Tao Zhang Donald Porter Radu Sion Stony Brook University & Stony Brook University & Stony Brook University UNC, Chapel Hill UNC, Chapel Hill ABSTRACT on Amazon’s Virtual Private Cloud (VPC) [2] (which provides The verified boot feature in recent Android devices, which strong security guarantees through network isolation) store deploys dm-verity, has been overwhelmingly successful in elim- data on untrusted storage devices residing in the public cloud. inating the extremely popular Android smart phone rooting For example, Amazon VPC file systems, object stores, and movement [25]. Unfortunately, dm-verity integrity guarantees databases reside on virtual block devices in the Amazon are read-only and do not extend to writable volumes. Elastic Block Storage (EBS). This paper introduces a new device mapper, dm-x, that This allows numerous attack vectors for a malicious cloud efficiently (fast) and reliably (metadata journaling) assures provider/untrusted software running on the server. For in- volume-level integrity for entire, writable volumes. In a direct stance, to ensure SEC-mandated assurances of end-to-end disk setup, dm-x overheads are around 6-35% over ext4 on the integrity, banks need to guarantee that the external cloud raw volume while offering additional integrity guarantees. For storage service is unable to remove log entries documenting cloud storage (Amazon EBS), dm-x overheads are negligible. financial transactions. Yet, without integrity of the storage device, a malicious cloud storage service could remove logs of a coordinated attack. -
Synology Router Rt2600ac Hardware Installation Guide
Synology Router RT2600ac Hardware Installation Guide Table of Contents Chapter 1: Meet Your Synology Router Package Contents 3 Synology Router at a Glance 4 Safety Instructions 5 Chapter 2: Set up Your Synology Router Install Antennas 6 Position Your Synology Router 7 Connect to Your Synology Router 7 Set up Synology Router Manager (SRM) 9 Appendix A: Specifications Appendix B: LED Indicator Table Synology_HIG_RouterRT2600ac_20160930 2 Chapter Meet Your Synology Router 1 Thank you for purchasing this Synology product! Before setting up your new Synology Router, please check the package contents to verify that you have received all of the items below. Also, make sure to read the safety instructions carefully to avoid harming yourself or damaging your Synology Router. Note: All images below are for illustrative purposes only, and may differ from the actual product. Package Contents Main unit x 1 AC power adapter x 1 RJ-45 LAN cable x 1 Antenna x 4 3 Chapter 1: Meet Your Synology Router Synology Router at a Glance No. Article Name Location Description 1 Antenna Base Install the included antennas here. 2 Power Button Press to power on/off the Synology Router. 3 Power Port Connect the AC power adapter here. Press and hold for four seconds (Soft Reset) or for ten seconds (Hard 4 RESET Button Rear Panel Reset). Connect an external drive, USB printer, or other types of USB devices 5 USB 2.0 Port here. Connect a network cable from the ISP modem into this port to establish 6 WAN Port WAN connection. 7 LAN Port Connect network cables into these ports to establish LAN connection. -
ECE 598 – Advanced Operating Systems Lecture 19
ECE 598 { Advanced Operating Systems Lecture 19 Vince Weaver http://web.eece.maine.edu/~vweaver [email protected] 7 April 2016 Announcements • Homework #7 was due • Homework #8 will be posted 1 Why use FAT over ext2? • FAT simpler, easy to code • FAT supported on all major OSes • ext2 faster, more robust filename and permissions 2 btrfs • B-tree fs (similar to a binary tree, but with pages full of leaves) • overwrite filesystem (overwite on modify) vs CoW • Copy on write. When write to a file, old data not overwritten. Since old data not over-written, crash recovery better Eventually old data garbage collected • Data in extents 3 • Copy-on-write • Forest of trees: { sub-volumes { extent-allocation { checksum tree { chunk device { reloc • On-line defragmentation • On-line volume growth 4 • Built-in RAID • Transparent compression • Snapshots • Checksums on data and meta-data • De-duplication • Cloning { can make an exact snapshot of file, copy-on- write different than link, different inodles but same blocks 5 Embedded • Designed to be small, simple, read-only? • romfs { 32 byte header (magic, size, checksum,name) { Repeating files (pointer to next [0 if none]), info, size, checksum, file name, file data • cramfs 6 ZFS Advanced OS from Sun/Oracle. Similar in idea to btrfs indirect still, not extent based? 7 ReFS Resilient FS, Microsoft's answer to brtfs and zfs 8 Networked File Systems • Allow a centralized file server to export a filesystem to multiple clients. • Provide file level access, not just raw blocks (NBD) • Clustered filesystems also exist, where multiple servers work in conjunction. -
Synology Rackstation RS1221RP+ Hardware Installation Guide
Synology NAS RS1221RP+ Hardware Installation Guide Table of Contents Chapter 1: Before You Start Package Contents 3 Synology RS1221RP+ at a Glance 4 System Modes and LED Indicators 6 Other LED Indicators 8 Hardware Specification 9 Spare Parts 10 Optional Accessories 10 Safety Instructions 11 Chapter 2: Hardware Setup Tools and Parts for Component Installation 12 Install Drives 12 Install Memory Modules 14 Install a PCle Add-in Card 17 Mount the Synology NAS to a 4-Post Rack 18 Start up Your Synology NAS 20 Chapter 3: System Maintenance Replace System Fan 21 Replace Power Supply Unit (PSU) 23 Chapter 4: Install DSM on Synology NAS Install DSM with Web Assistant 24 Learn More 24 Synology_HIG_RS1221RP+_20200928 2 Chapter Before You Start 1 Thank you for purchasing this Synology product! Before setting up your new Synology NAS, please check the package contents to verify that you have received the items below. Also, make sure to read the safety instructions carefully to avoid harming yourself or damaging your Synology NAS. Note: All images below are for illustrative purposes only, and may differ from the actual product. Package Contents Main unit x 1 AC power cord x 2 Screws for 3.5" drives x 36 Screws for 2.5" drives x 36 Drive tray key x 2 3 Synology RS1221RP+ at a Glance 1 23 4 5 6 7 7 8 9 10 11 12 13 8 14 15 No. Article Name Location Description Displays the power status of your Synology NAS. For more 1 POWER Indicator information, see "System Modes and LED Indicators". -
NOVA: a Log-Structured File System for Hybrid Volatile/Non
NOVA: A Log-structured File System for Hybrid Volatile/Non-volatile Main Memories Jian Xu and Steven Swanson, University of California, San Diego https://www.usenix.org/conference/fast16/technical-sessions/presentation/xu This paper is included in the Proceedings of the 14th USENIX Conference on File and Storage Technologies (FAST ’16). February 22–25, 2016 • Santa Clara, CA, USA ISBN 978-1-931971-28-7 Open access to the Proceedings of the 14th USENIX Conference on File and Storage Technologies is sponsored by USENIX NOVA: A Log-structured File System for Hybrid Volatile/Non-volatile Main Memories Jian Xu Steven Swanson University of California, San Diego Abstract Hybrid DRAM/NVMM storage systems present a host of opportunities and challenges for system designers. These sys- Fast non-volatile memories (NVMs) will soon appear on tems need to minimize software overhead if they are to fully the processor memory bus alongside DRAM. The result- exploit NVMM’s high performance and efficiently support ing hybrid memory systems will provide software with sub- more flexible access patterns, and at the same time they must microsecond, high-bandwidth access to persistent data, but provide the strong consistency guarantees that applications managing, accessing, and maintaining consistency for data require and respect the limitations of emerging memories stored in NVM raises a host of challenges. Existing file sys- (e.g., limited program cycles). tems built for spinning or solid-state disks introduce software Conventional file systems are not suitable for hybrid mem- overheads that would obscure the performance that NVMs ory systems because they are built for the performance char- should provide, but proposed file systems for NVMs either in- acteristics of disks (spinning or solid state) and rely on disks’ cur similar overheads or fail to provide the strong consistency consistency guarantees (e.g., that sector updates are atomic) guarantees that applications require. -
Oracle® Linux 7 Managing File Systems
Oracle® Linux 7 Managing File Systems F32760-07 August 2021 Oracle Legal Notices Copyright © 2020, 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. -
Filesystem Considerations for Embedded Devices ELC2015 03/25/15
Filesystem considerations for embedded devices ELC2015 03/25/15 Tristan Lelong Senior embedded software engineer Filesystem considerations ABSTRACT The goal of this presentation is to answer a question asked by several customers: which filesystem should you use within your embedded design’s eMMC/SDCard? These storage devices use a standard block interface, compatible with traditional filesystems, but constraints are not those of desktop PC environments. EXT2/3/4, BTRFS, F2FS are the first of many solutions which come to mind, but how do they all compare? Typical queries include performance, longevity, tools availability, support, and power loss robustness. This presentation will not dive into implementation details but will instead summarize provided answers with the help of various figures and meaningful test results. 2 TABLE OF CONTENTS 1. Introduction 2. Block devices 3. Available filesystems 4. Performances 5. Tools 6. Reliability 7. Conclusion Filesystem considerations ABOUT THE AUTHOR • Tristan Lelong • Embedded software engineer @ Adeneo Embedded • French, living in the Pacific northwest • Embedded software, free software, and Linux kernel enthusiast. 4 Introduction Filesystem considerations Introduction INTRODUCTION More and more embedded designs rely on smart memory chips rather than bare NAND or NOR. This presentation will start by describing: • Some context to help understand the differences between NAND and MMC • Some typical requirements found in embedded devices designs • Potential filesystems to use on MMC devices 6 Filesystem considerations Introduction INTRODUCTION Focus will then move to block filesystems. How they are supported, what feature do they advertise. To help understand how they compare, we will present some benchmarks and comparisons regarding: • Tools • Reliability • Performances 7 Block devices Filesystem considerations Block devices MMC, EMMC, SD CARD Vocabulary: • MMC: MultiMediaCard is a memory card unveiled in 1997 by SanDisk and Siemens based on NAND flash memory. -
News Announcement Announcement
NEWS ANNOUNCEMENT DVBLogic , Synology and PCTV Systems Working Together to Bring Extended Freedom to TV at Home DVBLink Package Turns Synology NAS into Rich Featured Centre of Connected TV Experience Berlin, 12 September 2012 News Facts • DVBLink Package for up to four TV tuner s runs on most Synology NAS • Supports all popular DVB TV standards in parallel • Optimized for TV tuners from PCTV Systems • Live TV and recorded shows on DLNA enabled TVs and CE devices as well as computers (Windows, Mac and Linux) • Schedule and manage recordings via web interface and DVBLink Mobile Client Apps for iOS, Android and Win dows Phone • Electronic program guides (EPG) on all clients within the home network • DVBLink TV Server for Time-shift TV on all streaming clients Synology NAS turning the NAS • Stand-alone solution - works without a PC into a personal video recorder (PVR) and server for Live TV. Porting the DVBLink software into a Synology NAS package brings TV streaming, remote recording and EPG to NAS devices further freeing TV from being stuck on CE devices or in PC environments. Attached to any home network and equipped with a PCTV tuner, the NAS device becomes the central TV device at home. T he DVBLink App makes Live- TV and recorded content available on a number of clients throughout the house. Managing recordings and browsing the EPG is also available on mobile phones in the same Wi Fi thanks to the DVBLink Mobile Client Apps. All configuration and management of the Package is done via a web interface. A pure CE TV experience brings easy access to channels and programs on favourite TV device, needs no fiddling around with softwa re installations and only those devices up and running that are really necessary. -
NAKIVO Backup & Replication V10.1
What’s New NAKIVO Backup & Replication v10.1 What’s New www.nakivo.com 1 What’s New What’s New in Backup for Microsoft Office 365 With NAKIVO Backup & Replication, businesses can ensure that their Microsoft Office 365 data is always accessible and recoverable when they face data loss events and ransomware attacks. With version 10.1, NAKIVO expands the functionality of Backup for Microsoft Office 365 to include protection for OneDrive for Business in addition to Exchange Online. Now you can use NAKIVO Backup & Replication to back up Exchange mailboxes and OneDrive for Business data and perform granular recovery of emails, attachments, files and folders. NAKIVO Backup & Replication is an all-in-one data protection solution for virtual, physical, cloud and SaaS environments. Customers can improve recovery times, reduce storage costs, shrink backup windows and automate data protection with a range of backup and recovery features. See for yourself how well NAKIVO Backup & Replication works in your environment with the 15-day Free Trial. OneDrive for Business Backup Backup for Microsoft Office 365 with NAKIVO Backup & Replication helps businesses to mitigate the risk of data loss by offering cost-effective backup and instant recovery for OneDrive for Business. Customers can: • Perform incremental backups of OneDrive • Locate OneDrive objects quickly by searching for Business data backups by file or folder name • Instantly recover OneDrive files and folders • Protect up to thousands of OneDrive for back to the original OneDrive account or Business user accounts with a single software different accounts deployment 2 What’s New Improvements • Ability to use locking functionality on a Backup • The Director service can now be restarted Repository so it can be used by only one directly from the web interface.