DOCSLIB.ORG

Fit for the Future

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Fit for the Future KNOW-HOW Ext4 The new Ext4 filesystem FIT FOR THE FUTURE The newest child in the Ext filesystem family provides better performance and supports bigger filesystems. Are you ready for Ext4? Julien BY MARCEL HILZINGER T r omeur , F o t olia inux came of age with the intro- strategy lets users around the world con- Another major change with Ext4 is the duction of the Ext2 filesystem, tinue to use the stable Ext3 while the de- use of extents. An extent is a contiguous Land Ext3 was the first journaling velopers integrate and test a new round area of additional disk space saved with filesystem to make it into the kernel. of enhancements. Ext4, the next genera- a file. The purpose of an extent is to en- Through the years, the Ext (Extended) tion of the Extended filesystem, is now sure that later changes will be stored in filesystem family has held an important available for users. We took a look at the same location as the original file. Ex- place in Linux, and Ext remains a popular Ext4 to see how it compares with other tents reduce fragmentation and improve choice for users around the world. But popular filesystem options. write speeds. Several other popular file- the venerable Ext code base is showing systems, such as Reiser4, NTFS, and the signs of age. Several months ago, devel- What Changes? Macintosh HPS filesystem, already sup- opers began to discuss the problem of Ext4 moves to better 64-bit support, port extents. adding new features to Ext3 while main- which leads to several other enhance- Backward compatibility was also a taining the stability and compatibility of ments. One important benefit unveiled goal for the Ext4 developers: You can the code [1]. Meanwhile, several initia- with Ext4 is an increase in the maximum mount an Ext4 partition as Ext3, and tives offered enhancements to the filesys- filesystem size. Ext3’s maximum filesys- you can mount an Ext3 partition as Ext4 tem that were too fundamental to inte- tem size of 8TB (with a default block (with the ext4dev filesystem type). Un- grate easily but too important to ignore. size of 4KB) was once considered huge, fortunately, to achieve this Ext3/ Ext4 The solution proposed by the develop- but contemporary hardware cries out for compatibility, you have to turn off Ext4’s ers was to fork the code and start work more. Ext4 now supports filesystems of extent feature, which is one of the major on a new filesystem called Ext4. This up to 1024 petabytes (PB). performance benefits of Ext4. 40 ISSUE 79 JUNE 2007 WWW.LINUX - MAGAZINE.COM Ext4 KNOW-HOW If you are interested in testing Ext4, you only want to add Ext4, need a current kernel and the usual de- just keep pressing Enter veloper tools: make, GCC, and glibc- to accept the defaults. devel. In our lab, we used kernel 2.6.20. Note that the system will Working as root, unpack the sources in not use Ext4 by default. the /usr/src directory and create a link of To change this, you need /usr/src/linux that points to the sources: to open the .config file and look for the follow- cp linux-2.6.20.tar.bz2 /usr/src ing entry: cd /usr/src tar xvfj linux-2.6.20.tar.bz2 # CONFIG_EXT4DEV_FS U ln -s linux-2.6.20 linux is not set To let the kernel know which kernel ele- Remove the pound sign ments you want to compile as modules, at the start of the line you need to create a .config file in /usr/ and change the entry to src/linux. To do so, you can issue either CONFIG_EXT4DEV_ Figure 1: To make sure the kernel understands Ext4, you need the make menuconfig or make xconfig FS=m (Figure 1). To to enable the corresponding option in your .config file. command. Because the manual system experiment with Ext4 on with its multitude of options is not easy, your root partition, you will need to make modules_install you might prefer to use the current ker- build the filesystem into the kernel make install nel as the basis for the new configura- rather than using a module. In this case, tion and just add the differences for the change the entry to CONFIG_EXT4DEV_ Most distributions will set up the initial new kernel version. To do so, copy the FS=y, launch make oldconfig again, and ramdisk (initrd) at this point and also /boot/config-kernelversion file to /usr/ then answer a few questions about Ext4 modify the bootloader. When you reboot src/linux and save the file as .config. The (Figure 2). your machine, you should be able to se- following command should do the trick Most current distributions use access lect the new kernel from the Grub menu. for most distributions: control lists (ACLs) and extended attri- Installing the new kernel will not affect butes to support more granular control your existing installation. cp /boot/config$(uname -r) U over user privileges. If the mount com- /usr/src/linux/.config mand output shows you entries for acl Working with Ext4 or user_xattr at the command line, you To create an Ext4 partition, you need a Again working as root, enter the make will need to enable these features on recent version of E2fsprogs-Tools [2]. oldconfig command in the /usr/src/linux Ext4 too. So when you are prompted to Users of SUSE Linux will find the current directory to create a new kernel from the enable EXT4DEV_FS_XATTR and SUSE kernel version 2.6.20 and match- existing configuration file. For each EXT4DEV_FS_POSIX_ACL, don’t forget ing E2fsprogrs at suse. com [3] or open- change, the system will prompt you for to say y. SUSE. org [4]. When you install this ker- whether you want the change and how You need security labels (EXT4DEV_ nel, make sure you don’t enter the rpm you want to implement it. Depending on FS_SECURITY) to support SElinux. Make -Uvh command, but use rpm -ivh instead your kernel version, you might need to sure you avoid enabling debugging sup- to keep the openSUSE 10.2 kernel. answer a number of questions. If you port for JBD2 because this will slow the To install Ext2-Tools, just follow the filesystem down. make enables debug- usual steps: ./configure, make, and (as Roadwork Ahead! ging support for JBD (JBD_SUPPORT) by root) make install. If an error occurs at default. the make step, you will probably need Athough Ext4 has officially been part of Linux since kernel 2.6.19, work on the After making your de- new filesystem is far from complete. cisions, type make old- Takashi Sato, for example, is currently config to write the new working on an online re-sizer that .config file, which now checks Ext4 for fragmentation on the fly has Ext4 support en- and corrects any issues it finds. The abled. Then run make to finished Ext4 product will also include start building the kernel. an undelete function. Some of these Depending on how fast new features, however, mean changing the filesystem format, and this could your machine is, this cause issues with existing Ext4 parti- can take a couple of tions. Given the current pace of develop- hours. After completing ment, you might want to think twice the kernel build, enter before moving to Ext3’s successor, the following commands although our tests did not identify any to install the module Figure 2: The second time you run make oldconfig, you only stability problems. and the kernel: need to answer questions on Ext4. WWW.LINUX - MAGAZINE.COM ISSUE 79 JUNE 2007 41 KNOW-HOW Ext4 �������������������� ������������������� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���������� ���� ���� ���� ������� ���� ���� ������� ���� ���� ������� ������� ���� ���� ��� ��� ��� ��� ��� ��� ��� ��� ����������� ���������� ����� ���� Figure 3: Ext4 writes a 1GB file slightly faster than ReiserFS in a Figure 5: Without extents, Ext4 writes far more slowly and drops blockwise write operation, and Ext4 is far faster than Ext3. down to the level of Ext3. to install the texinfo package on your commit=seconds option might be of The performance effect of the extents machine. After installing the package, interest. The interval you specify here feature is clearly demonstrated by the just run make again. determines how often Ext4 will write results of the “Random Create” test. It To create a new partition in Ext4 for- data to disk. The default value is every makes sense that Ext4 loses out to Ext3 mat, enter mke2fs -j <partition>, re- five seconds. Higher values improve here because it needs extra time to re- placing partition with the required de- performance and can also save power. serve storage space for the extents. This vice file name. You could also use the But note that this compromises the extra work is not required on deleting GUI to create a new Ext3 partition. After safety of any data that have not yet been files, and this is where Ext4 overtakes doing so, mount the partition by enter- saved. This said, our benchmarks failed Ext3 and ReiserFS, which comes in last ing mount -t ext4dev <partition> to reveal any significant difference when in the Bonnie++ stress tests. <mountpoint>. The kernel will auto- we set this option to commit=60. Finally, we wanted to know how fast matically load the ext4dev module. For our first tests with the developer Ext4 is without extents. Figure 5 shows If you intend to use Ext4’s extents fea- version of Ext4, we put the filesystem the results of the Slow.c benchmarks ture, you need to add -o extents to the through its paces with the Bonnie++ with a 1GB test file.
Load more

Recommended publications
  • Study of File System Evolution
    Study of File System Evolution Swaminathan Sundararaman, Sriram Subramanian Department of Computer Science University of Wisconsin {swami, srirams} @cs.wisc.edu Abstract File systems have traditionally been a major area of file systems are typically developed and maintained by research and development. This is evident from the several programmer across the globe. At any point in existence of over 50 file systems of varying popularity time, for a file system, there are three to six active in the current version of the Linux kernel. They developers, ten to fifteen patch contributors but a single represent a complex subsystem of the kernel, with each maintainer. These people communicate through file system employing different strategies for tackling individual file system mailing lists [14, 16, 18] various issues. Although there are many file systems in submitting proposals for new features, enhancements, Linux, there has been no prior work (to the best of our reporting bugs, submitting and reviewing patches for knowledge) on understanding how file systems evolve. known bugs. The problems with the open source We believe that such information would be useful to the development approach is that all communication is file system community allowing developers to learn buried in the mailing list archives and aren’t easily from previous experiences. accessible to others. As a result when new file systems are developed they do not leverage past experience and This paper looks at six file systems (Ext2, Ext3, Ext4, could end up re-inventing the wheel. To make things JFS, ReiserFS, and XFS) from a historical perspective worse, people could typically end up doing the same (between kernel versions 1.0 to 2.6) to get an insight on mistakes as done in other file systems.
    [Show full text]
  • Silicon Graphics, Inc. Scalable Filesystems XFS & CXFS
    Silicon Graphics, Inc. Scalable Filesystems XFS & CXFS Presented by: Yingping Lu January 31, 2007 Outline • XFS Overview •XFS Architecture • XFS Fundamental Data Structure – Extent list –B+Tree – Inode • XFS Filesystem On-Disk Layout • XFS Directory Structure • CXFS: shared file system ||January 31, 2007 Page 2 XFS: A World-Class File System –Scalable • Full 64 bit support • Dynamic allocation of metadata space • Scalable structures and algorithms –Fast • Fast metadata speeds • High bandwidths • High transaction rates –Reliable • Field proven • Log/Journal ||January 31, 2007 Page 3 Scalable –Full 64 bit support • Large Filesystem – 18,446,744,073,709,551,615 = 264-1 = 18 million TB (exabytes) • Large Files – 9,223,372,036,854,775,807 = 263-1 = 9 million TB (exabytes) – Dynamic allocation of metadata space • Inode size configurable, inode space allocated dynamically • Unlimited number of files (constrained by storage space) – Scalable structures and algorithms (B-Trees) • Performance is not an issue with large numbers of files and directories ||January 31, 2007 Page 4 Fast –Fast metadata speeds • B-Trees everywhere (Nearly all lists of metadata information) – Directory contents – Metadata free lists – Extent lists within file – High bandwidths (Storage: RM6700) • 7.32 GB/s on one filesystem (32p Origin2000, 897 FC disks) • >4 GB/s in one file (same Origin, 704 FC disks) • Large extents (4 KB to 4 GB) • Request parallelism (multiple AGs) • Delayed allocation, Read ahead/Write behind – High transaction rates: 92,423 IOPS (Storage: TP9700)
    [Show full text]
  • BSD UNIX Toolbox 1000+ Commands for Freebsd, Openbsd
    76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iii BSD UNIX® TOOLBOX 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD®Power Users Christopher Negus François Caen 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page ii 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page i BSD UNIX® TOOLBOX 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page ii 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iii BSD UNIX® TOOLBOX 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD®Power Users Christopher Negus François Caen 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iv BSD UNIX® Toolbox: 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD® Power Users Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2008 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-0-470-37603-4 Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 Library of Congress Cataloging-in-Publication Data is available from the publisher. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permis- sion should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, or online at http://www.wiley.com/go/permissions.
    [Show full text]
  • W4118: File Systems
    W4118: file systems Instructor: Junfeng Yang References: Modern Operating Systems (3rd edition), Operating Systems Concepts (8th edition), previous W4118, and OS at MIT, Stanford, and UWisc Outline File system concepts . What is a file? . What operations can be performed on files? . What is a directory and how is it organized? File implementation . How to allocate disk space to files? 1 What is a file User view . Named byte array • Types defined by user . Persistent across reboots and power failures OS view . Map bytes as collection of blocks on physical storage . Stored on nonvolatile storage device • Magnetic Disks 2 Role of file system Naming . How to “name” files . Translate “name” + offset logical block # Reliability . Must not lose file data Protection . Must mediate file access from different users Disk management . Fair, efficient use of disk space . Fast access to files 3 File metadata Name – only information kept in human-readable form Identifier – unique tag (number) identifies file within file system (inode number in UNIX) Location – pointer to file location on device Size – current file size Protection – controls who can do reading, writing, executing Time, date, and user identification – data for protection, security, and usage monitoring How is metadata stored? (inode in UNIX) 4 File operations int creat(const char* pathname, mode_t mode) int unlink(const char* pathname) int rename(const char* oldpath, const char* newpath) int open(const char* pathname, int flags, mode_t mode) int read(int fd, void* buf, size_t count); int write(int fd, const void* buf, size_t count) int lseek(int fd, offset_t offset, int whence) int truncate(const char* pathname, offset_t len) ..
    [Show full text]
  • Lecture 17: Files and Directories
    11/1/16 CS 422/522 Design & Implementation of Operating Systems Lecture 17: Files and Directories Zhong Shao Dept. of Computer Science Yale University Acknowledgement: some slides are taken from previous versions of the CS422/522 lectures taught by Prof. Bryan Ford and Dr. David Wolinsky, and also from the official set of slides accompanying the OSPP textbook by Anderson and Dahlin. The big picture ◆ Lectures before the fall break: – Management of CPU & concurrency – Management of main memory & virtual memory ◆ Current topics --- “Management of I/O devices” – Last week: I/O devices & device drivers – Last week: storage devices – This week: file systems * File system structure * Naming and directories * Efficiency and performance * Reliability and protection 1 11/1/16 This lecture ◆ Implementing file system abstraction Physical Reality File System Abstraction block oriented byte oriented physical sector #’s named files no protection users protected from each other data might be corrupted robust to machine failures if machine crashes File system components ◆ Disk management User – Arrange collection of disk blocks into files File File ◆ Naming Naming access – User gives file name, not track or sector number, to locate data Disk management ◆ Security / protection – Keep information secure Disk drivers ◆ Reliability/durability – When system crashes, lose stuff in memory, but want files to be durable 2 11/1/16 User vs. system view of a file ◆ User’s view – Durable data structures ◆ System’s view (system call interface) – Collection of bytes (Unix) ◆ System’s view (inside OS): – Collection of blocks – A block is a logical transfer unit, while a sector is the physical transfer unit.
    [Show full text]
  • CXFSTM Administration Guide for SGI® Infinitestorage
    CXFSTM Administration Guide for SGI® InfiniteStorage 007–4016–025 CONTRIBUTORS Written by Lori Johnson Illustrated by Chrystie Danzer Engineering contributions to the book by Vladmir Apostolov, Rich Altmaier, Neil Bannister, François Barbou des Places, Ken Beck, Felix Blyakher, Laurie Costello, Mark Cruciani, Rupak Das, Alex Elder, Dave Ellis, Brian Gaffey, Philippe Gregoire, Gary Hagensen, Ryan Hankins, George Hyman, Dean Jansa, Erik Jacobson, John Keller, Dennis Kender, Bob Kierski, Chris Kirby, Ted Kline, Dan Knappe, Kent Koeninger, Linda Lait, Bob LaPreze, Jinglei Li, Yingping Lu, Steve Lord, Aaron Mantel, Troy McCorkell, LaNet Merrill, Terry Merth, Jim Nead, Nate Pearlstein, Bryce Petty, Dave Pulido, Alain Renaud, John Relph, Elaine Robinson, Dean Roehrich, Eric Sandeen, Yui Sakazume, Wesley Smith, Kerm Steffenhagen, Paddy Sreenivasan, Roger Strassburg, Andy Tran, Rebecca Underwood, Connie Woodward, Michelle Webster, Geoffrey Wehrman, Sammy Wilborn COPYRIGHT © 1999–2007 SGI. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of SGI. LIMITED RIGHTS LEGEND The software described in this document is "commercial computer software" provided with restricted rights (except as to included open/free source) as specified in the FAR 52.227-19 and/or the DFAR 227.7202, or successive sections. Use beyond
    [Show full text]
  • 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.
    [Show full text]
  • Netinfo 2009-06-11 Netinfo 2009-06-11
    Netinfo 2009-06-11 Netinfo 2009-06-11 Microsoft släppte 2009-06-09 tio uppdateringar som täpper till 31 stycken säkerhetshål i bland annat Windows, Internet Explorer, Word, Excel, Windows Search. 18 av buggfixarna är märkta som kritiska och elva av dem är märkta som viktiga, uppdateringarna finns för både servrar och arbetsstationer. Säkerhetsuppdateringarna finns tillgängliga på Windows Update. Den viktigaste säkerhetsuppdateringen av de som släpptes är den för Internet Explorer 8. Netinfo 2009-06-11 Security Updates available for Adobe Reader and Acrobat Release date: June 9, 2009 Affected software versions Adobe Reader 9.1.1 and earlier versions Adobe Acrobat Standard, Pro, and Pro Extended 9.1.1 and earlier versions Severity rating Adobe categorizes this as a critical update and recommends that users apply the update for their product installations. These vulnerabilities would cause the application to crash and could potentially allow an attacker to take control of the affected system. Netinfo 2009-06-11 SystemRescueCd Description: SystemRescueCd is a Linux system on a bootable CD-ROM for repairing your system and recovering your data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system tools (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools). It is very easy to use: just boot the CDROM. The kernel supports most of the important file systems (ext2/ext3/ext4, reiserfs, reiser4, btrfs, xfs, jfs, vfat, ntfs, iso9660), as well as network filesystems (samba and nfs).
    [Show full text]
  • Zack's Kernel News
    KERNEL NEWS ZACK’S KERNEL NEWS ReiserFS Turmoil Their longer term plan, Alexander Multiport Card driver, again naming In light of recent events surrounding says, depends on what happens with himself the maintainer. Hans Reiser (http:// www. linux-maga- Hans. If Hans is released, the developers Jiri’s been submitting a number of zine. com/ issue/ 73/ Linux_World_News. intend to proceed as before. If he is not patches for these drivers, so it makes pdf), the question of how to continue released, Alexander’s best guess is that sense he would maintain them if he ReiserFS development came up on the the developers will try to appoint a wished; in any event, no other kernel linux-kernel mailing list. Alexander proxy to run Namesys. hacker has spoken up to claim the role. Lyamin from Hans’s Namesys company offered his take on the situation. He said Status of sysctl Filesystem Benchmarks that ReiserFS 3 has pretty much stabi- In keeping with Linus Torvalds’ recent Some early tests have indicated that ext4 lized into bugfix mode, though Suse assertions that it is never acceptable to is faster with disk writes than either ext3 folks had been adding new features like break user-space, Albert Cahalan volun- or Reiser4. There was general interest in ACL support. So ReiserFS 3 would go on teered to maintain the sysctl code if it these results, though the tests had some as before. couldn’t be removed. But Linus pointed problems (the tester thought delayed In terms of Reiser4, however, Alexan- out that really nothing actually used allocation was part of ext4, when that der said that he and the other Reiser de- sysctl (the implication being that it feature has not yet been merged into velopers were still addressing the techni- wouldn’t actually break anything to get Andrew Morton’s tree).
    [Show full text]
  • Journaling File Systems
    Linux Journaling File Systems Linux onzSeries Journaling File Systems Volker Sameske ([email protected]) Linux on zSeries Development IBM Lab Boeblingen, Germany Share Anaheim,California February27 –March 4,2005 Session 9257 ©2005 IBM Corporation Linux Journaling File Systems Agenda o File systems. • Overview, definitions. • Reliability, scalability. • File system features. • Common grounds & differences. o Volume management. • LVM, EVMS, MD. • Striping. o Measurement results. • Hardware/software setup. • throughput. • CPU load. 2 Session 9257 © 2005 IBM Corporation Linux Journaling File Systems A file system should... o ...store data o ...organize data o ...administrate data o ...organize data about the data o ...assure integrity o ...be able to recover integrity problems o ...provide tools (expand, shrink, check, ...) o ...be able to handle many and large files o ...be fast o ... 3 Session 9257 © 2005 IBM Corporation Linux Journaling File Systems File system-definition o Informally • The mechanism by which computer files are stored and organized on a storage device. o More formally, • A set of abstract data types that are necessary for the storage, hierarchical organization, manipulation, navigation, access and retrieval of data. 4 Session 9257 © 2005 IBM Corporation Linux Journaling File Systems Why a journaling file system? o Imagine your Linux system crashs while you are saving an edited file: • The system crashs after the changes have been written to disk à good crash • The system crashs before the changes have been written to disk à bad crash but bearable if you have an older version • The sytem crashs just in the moment your data will be written: à very bad crash your file could be corrupted and in worst case the file system could be corrupted à That‘s why you need a journal 5 Session 9257 © 2005 IBM Corporation Linux Journaling File Systems Somefilesystemterms o Meta data • "Data about the data" • File system internal data structure (e.g.
    [Show full text]
  • Operating Systems Lecture #5: File Management
    Operating Systems Lecture #5: File Management Written by David Goodwin based on the lecture series of Dr. Dayou Li and the book Understanding Operating Systems 4thed. by I.M.Flynn and A.McIver McHoes (2006) Department of Computer Science and Technology, University of Bedfordshire. Operating Systems, 2013 25th February 2013 Outline Lecture #5 File Management David Goodwin 1 Introduction University of Bedfordshire 2 Interaction with the file manager Introduction Interaction with the file manager 3 Files Files Physical storage 4 Physical storage allocation allocation Directories 5 Directories File system Access 6 File system Data compression summary 7 Access 8 Data compression 9 summary Operating Systems 46 Lecture #5 File Management David Goodwin University of Bedfordshire Introduction 3 Interaction with the file manager Introduction Files Physical storage allocation Directories File system Access Data compression summary Operating Systems 46 Introduction Lecture #5 File Management David Goodwin University of Bedfordshire Introduction 4 Responsibilities of the file manager Interaction with the file manager 1 Keep track of where each file is stored Files 2 Use a policy that will determine where and how the files will Physical storage be stored, making sure to efficiently use the available storage allocation space and provide efficient access to the files. Directories 3 Allocate each file when a user has been cleared for access to File system it, and then record its use. Access 4 Deallocate the file when the file is to be returned to storage, Data compression and communicate its availability to others who may be summary waiting for it. Operating Systems 46 Definitions Lecture #5 File Management field is a group of related bytes that can be identified by David Goodwin University of the user with a name, type, and size.
    [Show full text]
  • Introduction to ISO 9660
    Disc Manufacturing, Inc. A QUIXOTE COMPANY Introduction to ISO 9660, what it is, how it is implemented, and how it has been extended. Clayton Summers Copyright © 1993 by Disc Manufacturing, Inc. All rights reserved. WHO IS DMI? Disc Manufacturing, Inc. (DMI) manufactures all compact disc formats (i.e., CD-Audio, CD-ROM, CD-ROM XA, CDI, PHOTO CD, 3DO, KARAOKE, etc.) at two plant sites in the U.S.; Huntsville, AL, and Anaheim, CA. To help you, DMI has one of the largest Product Engineering/Technical Support staff and sales force dedicated solely to CD-ROM in the industry. The company has had a long term commitment to optical disc technology and has performed developmental work and manufactured (laser) optical discs of various types since 1981. In 1983, DMI manufactured the first compact disc in the United States. DMI has developed extensive mastering expertise during this time and is frequently called upon by other companies to provide special mastering services for products in development. In August 1991, DMI purchased the U.S. CD-ROM business from the Philips and Du Pont Optical Company (PDO). PDO employees in sales, marketing and technical services were retained. DMI is a wholly-owned subsidiary of Quixote Corporation, a publicly owned corporation whose stock is traded on the NASDAQ exchange as QUIX. Quixote is a diversified technology company composed of Energy Absorption Systems, Inc. (manufactures highway crash cushions), Stenograph Corporation (manufactures shorthand machines and computer systems for court reporting) and Disc Manufacturing, Inc. We would be pleased to help you with your CD project or answer any questions you may have.
    [Show full text]