DOCSLIB.ORG

DEFRAG YOUR HARD DRIVE Should You Or Shouldn’T You? Beginners’ Kaffee Klatch Presented by Bill Wilkinson June 20, 2009

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DEFRAG YOUR HARD DRIVE Should You Or Shouldn’T You? Beginners’ Kaffee Klatch Presented by Bill Wilkinson June 20, 2009 DEFRAG YOUR HARD DRIVE Should You or Shouldn’t You? Beginners’ Kaffee Klatch Presented by Bill Wilkinson June 20, 2009 FRAGMENTATION : Refers to the condition of a disk in which files are divided into pieces scattered around the disk. It occurs naturally when you use a disk frequently, creating, deleting, and modifying files. At some point, the operating system needs to store parts of a file in noncontiguous clusters. This is entirely invisible to users, but it can slow down the speed at which data is accessed because the disk drive must search through different parts of the disk to put together a single file. Whether or not this slow down is significant or even observable by the user is an issue that appears not yet to be resolved! It might surprise you to find that the data that appears to be so neatly organized inside files and folders on your computer are actually more jumbled than a bucket full of worms. While a computer’s hard drive is very precise in remembering where it has stored your data, it does tend to store it in some strange places from time to time. Unlike a neatly organized filing cabinet, your computer breaks up large files into smaller file fragments tailored to fill the first available free spaces on your hard drive. Your Hard Drive and Your Daily Newspaper – a metaphor To better understand the concept of defragging a hard drive, imagine picking up today’s newspaper and reading a front-page article. After a few paragraphs, you are asked to turn to another page to continue reading the story. It takes some time to open the paper, turn to the proper page, and find the story to continue reading. Now, imagine that you are required to move to a different page after each paragraph of the story. It would take a lot more time to read the fragmented story than it would have if the story was printed on a single page. The same concept applies to your hard drive. It takes time for the mechanical components of your hard drive to skip all over your drive and locate all of the fragments of a single file and place them in the proper order. Over time, hard drives can become so fragmented that they appear to boot slower or seem sluggish when performing common tasks. Defragmenting your hard drive will take most of the file fragments that are scattered about your drive and organize them into complete files. Because your Page 1 of 6 hard drive can now read the fragments as one organized file, your computer, in theory at least, should perform faster than it did in its fragmented state. When you save a file for the first time on a freshly formatted hard disk, Windows writes it in contiguous clusters. Because all the clusters that hold individual pieces of the file are physically adjacent to one another, the mechanical components of the hard disk can work very efficiently, scooping up data in one smooth operation. When you add information to an existing file, however, the file system has to allocate more clusters for storage, typically in a different physical location on the disk. As you delete files, you create gaps in the once-tidy arrangement of contiguously stored files. As you save new files, especially large ones, the file system uses all these bits of free space, scattering them over the hard disk into many noncontiguous pieces. The resulting inefficiency in storage is called fragmentation; each time you open or save a file on a badly fragmented disk, disk performance suffers, sometimes dramatically, because the disk heads have to spend extra time moving from cluster to cluster before they can begin reading or writing data. Organizing these scattered file fragments into contiguous segments on your hard drive is called defragmenting . Windows Disk Defragmenter Many Windows users have described the Windows Disk Defrag program as a “clunker”—very slow and not worth the time it takes to execute. However, if you want to do it Microsoft’s way, then make sure you run the following two Windows utilities BEFORE defragmenting your hard drive. If you don’t want to do it Microsoft’s way, then scroll down to the bottom of this document (page six) and download and install the FREE Advanced SystemCare program. Disk Cleanup. Windows accumulates many “junk” files during normal use, such as temporary ones. The Disk Cleanup utility makes it easy to delete these unnecessary files from your hard drive and free up the space for other uses. (The Disk Defragmenter does not defragment files in the Recycle Bin, so it is advisable to empty the Recycle Bin before defragmenting.) Click Start , All Programs , Accessories , System Tools , and Disk Cleanup . Choose the drive on which you want to work and then click OK. Click the items you want to delete, then click OK and Yes. Drive (Disk) scanning. Next, you should give your hard drive a basic checkup. A drive-scanning utility can give you a heads-up on some possible problems your hard drive may be facing. These utilities check for errors in file storage and Page 2 of 6 management, which can indicate anything from a common electronic hiccup to a potential drive failure on the horizon. In WinXP and Vista, the program is called Check Disk (ChkDsk). Launch Windows Explorer by tapping the E key while depressing the Windows key. Right-click your hard drive’s icon ( Local Disk C ) in the left pane, then click Properties . Now go to the Tools tab. Under Error Checking click the Check Now button. Under check disk options , check both " Automatically fix file system errors " and " Scan for and attempt recovery of bad sectors ". Click Start . On the information window, click Yes . Reboot the computer. The Check Disk application will start when you reboot your computer. Warning! The Check Disk application when executed can be quite time-consuming, perhaps hours, based on the size and speed of your system. Both Windows XP and Vista come with a defragmentation tool called Disk Defragmenter. The Windows Disk Defragmenter can only defragment files that are not in use. So, although you can continue to work as your computer is defragmenting its hard drive, you will get a more complete defragmentation if you do not have programs or files open during the defragmentation process. Therefore, to get a more complete defragmentation, you should reboot your computer into Safe Mode . A sure approach to accessing Safe Mode is to depress the F8 key and keep it depressed as soon as press the start button on your computer. Use your up arrow key to move up to a Safe Mode choice and press <Enter>. This prevents any applications from loading when your computer boots, including your antivirus and firewall software. With no programs or files open, the utility is free to defragment every file on the drive, with the exception of certain Windows files that are in use. While in Safe Mode in XP, you can access Windows’ Disk Defragmenter by selecting Start , All Programs , Accessories , System Tools , and clicking Disk Defragmenter . In Vista, click on the Start Button and in the Search Box, type disk defragmenter . When the Disk Defragmenter utility opens, you will need to click the drive you wish to defragment if you have more than one hard drive. Once you have selected the drive you wish to defragment, you will be presented with two options: Analyze or Defragment . In XP, the Analyze button creates two graphs that can help you determine how badly fragmented the files on your hard drive have become. The first graph shows the number of Fragmented Files vs. Contiguous Files. Unmovable Files are represented in green and Free Space is shown in white. The second graph will show the expected level of file fragmentation should you decide to defragment the drive. If you choose to analyze your drive before Page 3 of 6 defragmenting it, Windows will give you its suggestion as to whether you should defragment the drive. You also can click the View Report button to get a more detailed analysis of the fragmented files that were found on your computer. (Don’t defrag just because Microsoft tells you to do so. You would be defragging all the time if you took their advice!) When you click the Defragment button, the utility simply begins to reorganize your file fragments. Smaller fragments are shifted into free areas of the drive and slowly sorted and resaved as contiguous files. The amount of time required to complete the defragmentation process will vary based on the size of the hard drive, available free space (you must have a minimum of 15%), amount of data stored on the drive, speed of the drive, and the level of file fragmentation. A badly fragmented hard drive could take hours to defragment, but the handy graphs provided in the Disk Defragmenter interface will constantly update you on the status of the defragmentation, ensuring that your computer is working and not locked up. Once the defragmentation process is complete, you can exit the Disk Defragmenter utility. If you performed your defragmentation in Safe Mode, you will need to restart your computer to put it into Normal Mode again. For Windows Vista users , the Windows Disk Defragmenter works in a very similar way, except that all of the progress graphs have been removed and the only feedback you receive is a small box telling you that the computer is defragmenting. Vista computers may experience more fragmentation than WinXP-based systems because of all of the disk swapping that takes place.
Load more

Recommended publications
  • Fragmentation in Large Object Repositories
    Fragmentation in Large Object Repositories Experience Paper Russell Sears Catharine van Ingen University of California, Berkeley Microsoft Research [email protected] [email protected] ABSTRACT 1. INTRODUCTION Fragmentation leads to unpredictable and degraded application Application data objects continue to increase in size. performance. While these problems have been studied in detail Furthermore, the increasing popularity of web services and other for desktop filesystem workloads, this study examines newer network applications means that systems that once managed static systems such as scalable object stores and multimedia archives of “finished” objects now manage frequently modified repositories. Such systems use a get/put interface to store objects. versions of application data. Rather than updating these objects in In principle, databases and filesystems can support such place, typical archives either store multiple versions of the objects applications efficiently, allowing system designers to focus on (the V of WebDAV stands for “versioning” [25]), or simply do complexity, deployment cost and manageability. wholesale replacement (as in SharePoint Team Services [19]). Similarly, applications such as personal video recorders and Although theoretical work proves that certain storage policies media subscription servers continuously allocate and delete large, behave optimally for some workloads, these policies often behave transient objects. poorly in practice. Most storage benchmarks focus on short-term behavior or do not measure fragmentation. We compare SQL Applications store large objects as some combination of files in Server to NTFS and find that fragmentation dominates the filesystem and as BLOBs (binary large objects) in a database. performance when object sizes exceed 256KB-1MB. NTFS Only folklore is available regarding the tradeoffs.
    [Show full text]
  • 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.
    [Show full text]
  • Ext4 File System and Crash Consistency
    1 Ext4 file system and crash consistency Changwoo Min 2 Summary of last lectures • Tools: building, exploring, and debugging Linux kernel • Core kernel infrastructure • Process management & scheduling • Interrupt & interrupt handler • Kernel synchronization • Memory management • Virtual file system • Page cache and page fault 3 Today: ext4 file system and crash consistency • File system in Linux kernel • Design considerations of a file system • History of file system • On-disk structure of Ext4 • File operations • Crash consistency 4 File system in Linux kernel User space application (ex: cp) User-space Syscalls: open, read, write, etc. Kernel-space VFS: Virtual File System Filesystems ext4 FAT32 JFFS2 Block layer Hardware Embedded Hard disk USB drive flash 5 What is a file system fundamentally? int main(int argc, char *argv[]) { int fd; char buffer[4096]; struct stat_buf; DIR *dir; struct dirent *entry; /* 1. Path name -> inode mapping */ fd = open("/home/lkp/hello.c" , O_RDONLY); /* 2. File offset -> disk block address mapping */ pread(fd, buffer, sizeof(buffer), 0); /* 3. File meta data operation */ fstat(fd, &stat_buf); printf("file size = %d\n", stat_buf.st_size); /* 4. Directory operation */ dir = opendir("/home"); entry = readdir(dir); printf("dir = %s\n", entry->d_name); return 0; } 6 Why do we care EXT4 file system? • Most widely-deployed file system • Default file system of major Linux distributions • File system used in Google data center • Default file system of Android kernel • Follows the traditional file system design 7 History of file system design 8 UFS (Unix File System) • The original UNIX file system • Design by Dennis Ritche and Ken Thompson (1974) • The first Linux file system (ext) and Minix FS has a similar layout 9 UFS (Unix File System) • Performance problem of UFS (and the first Linux file system) • Especially, long seek time between an inode and data block 10 FFS (Fast File System) • The file system of BSD UNIX • Designed by Marshall Kirk McKusick, et al.
    [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]
  • Implementing Nfsv4 in the Enterprise: Planning and Migration Strategies
    Front cover Implementing NFSv4 in the Enterprise: Planning and Migration Strategies Planning and implementation examples for AFS and DFS migrations NFSv3 to NFSv4 migration examples NFSv4 updates in AIX 5L Version 5.3 with 5300-03 Recommended Maintenance Package Gene Curylo Richard Joltes Trishali Nayar Bob Oesterlin Aniket Patel ibm.com/redbooks International Technical Support Organization Implementing NFSv4 in the Enterprise: Planning and Migration Strategies December 2005 SG24-6657-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (December 2005) This edition applies to Version 5, Release 3, of IBM AIX 5L (product number 5765-G03). © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Preface . xiii The team that wrote this redbook. xiv Acknowledgments . xv Become a published author . xvi Comments welcome. xvii Part 1. Introduction . 1 Chapter 1. Introduction. 3 1.1 Overview of enterprise file systems. 4 1.2 The migration landscape today . 5 1.3 Strategic and business context . 6 1.4 Why NFSv4? . 7 1.5 The rest of this book . 8 Chapter 2. Shared file system concepts and history. 11 2.1 Characteristics of enterprise file systems . 12 2.1.1 Replication . 12 2.1.2 Migration . 12 2.1.3 Federated namespace . 13 2.1.4 Caching . 13 2.2 Enterprise file system technologies. 13 2.2.1 Sun Network File System (NFS) . 13 2.2.2 Andrew File System (AFS) .
    [Show full text]
  • External Flash Filesystem for Sensor Nodes with Sparse Resources
    External Flash Filesystem for Sensor Nodes with sparse Resources Stephan Lehmann Stephan Rein Clemens Gühmann stephan.lehmann@tu- stephan.rein@tu- clemens.guehmann@tu- berlin.de berlin.de berlin.de Wavelet Application Group Department of Energy and Automation Technology Chair of Electronic Measurement and Diagnostic Technology Technische Universität Berlin ABSTRACT for using just a few kilobytes of RAM, the source data must This paper describes a free filesystem for external flash mem- be accessible. Another memory intensive task concerns long- ory to be employed with low-complexity sensor nodes. The term sensor logs. system uses a standard secure digital (SD) card that can be easily connected to the serial port interface (SPI) or any A cost effective solution of this memory problem could be general input/output port of the sensor’s processor. The external flash memory. Flash memory is non-volatile and filesystem is evaluated with SD- cards used in SPI mode and therefore power failure safe. Flash memory can be obtained achieves an average random write throughput of about 40 either as raw flash or as standard flash devices such as USB- kByte/sec. For random write access throughputs larger than sticks or SD- cards. Raw flashes are pure flash chips which 400 kByte/sec are achieved. The filesystem allows for stor- do not provide a controller unit for wear levelling- that is, age of large amounts of sensor or program data and can assist a technique for prolonging the service life of the erasable more memory expensive algorithms. It requires 7 kByte of storage media - or garbage collection.
    [Show full text]
  • Total Defrag™ 2009
    Total Defrag™ 2009 User Manual Paragon Total Defrag™ 2009 2 User Manual CONTENTS Introduction ............................................................................................................................. 3 Key Features ............................................................................................................................ 3 Installation ............................................................................................................................... 3 Minimum System Requirements ....................................................................................................................3 Installation Procedure .....................................................................................................................................4 Basic Concepts ......................................................................................................................... 5 A Hard Disk Layout.........................................................................................................................................5 File Fragmentation...........................................................................................................................................6 Defragmentation ..............................................................................................................................................7 Interface Overview.................................................................................................................. 7 General
    [Show full text]
  • System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1
    SUSE Linux Enterprise Server 15 SP1 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1 An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to eciently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xiii
    [Show full text]
  • Identifying Common Reliability/Stability Problems Caused by File Fragmentation
    WHITE PAPER Identifying Common Reliability/Stability Problems Caused by File Fragmentation Think Faster.™ Visit us at Condusiv.com CT Reliability-Stability WP 12-03-01.indd 1 3/2/12 5:19 PM IDENTIFYING COMMON RELIABILITY/STABILITY PROBLEMS CAUSED BY FILE FRAGMENTATION II Table of Contents INTRODUCTION 1 AN OVERVIEW OF THE PROBLEM 1 RELIABILITY AND STABILITY ISSUES TRACEABLE TO FILE FRAGMENTATION 2 1. Crashes and system hangs 3 2. Slow backup time and aborted backup 5 3. File corruption and data loss 6 4. Boot-up issues 7 5. Errors in programs 7 6. RAM use and cache problems 8 7. Hard drive failures 9 CONTIGUOUS FILES = GREATER UP TIME 10 BIBLIOGRAPHY 11 CT Reliability-Stability WP 12-03-01.indd 2 3/2/12 5:19 PM IDENTIFYING COMMON RELIABILITY/STABILITY PROBLEMS CAUSED BY FILE FRAGMENTATION 1 Introduction Over the years, numerous manufacturers, third party analysts and labs have reported on the effects of disk/file fragmentation on system speed and performance. Defragmentation has also gained recognition for its critical role in addressing issues of system reliability and improved uptime, particularly since Microsoft’s decision to include a defragmentation utility in the Windows 2000 and newer operating systems. Disk fragmentation is In this white paper, we explain some of the most common reliability and downtime phenomena often the “straw that broke associated with fragmentation, and the technical reasons behind them. This includes a discussion the camel’s back” when of each of the most common occurrences documented by our R&D labs, customers (empirical noting issues of stability results presented), as well as others, in recent years.
    [Show full text]
  • Outline of Ext4 File System & Ext4 Online Defragmentation Foresight
    Outline of Ext4 File System & Ext4 Online Defragmentation Foresight LinuxCon Japan/Tokyo 2010 September 28, 2010 Akira Fujita <[email protected]> NEC Software Tohoku, Ltd. Self Introduction ▐ Name: Akira Fujita Japan ▐ Company: NEC Software Tohoku, Ltd. in Sendai, Japan. Sendai ● ▐ Since 2004, I have been working at NEC Software Tohoku developing Linux file system, mainly ext3 and ● ext4 filesystems. Tokyo Currently, I work on the quality evaluation of ext4 for enterprise use, and also develop the ext4 online defragmentation. Page 2 Copyright(C) 2010 NEC Software Tohoku, Ltd. All Rights Reserved. Outline ▐ What is ext4 ▐ Ext4 features ▐ Compatibility ▐ Performance measurement ▐ Recent ext4 topics ▐ What is ext4 online defrag ▐ Relevant file defragmentation ▐ Current status / future plan Page 3 Copyright(C) 2010 NEC Software Tohoku, Ltd. All Rights Reserved. What is ext4 ▐ Ext4 is the successor of ext3 which is developed to solve performance issues and scalability bottleneck on ext3 and also provide backward compatibility with ext3. ▐ Ext4 development began in 2006. Included in stable kernel 2.6.19 as EXPERIMENTAL (ext4dev). Since kernel 2.6.28, ext4 has been released as stable (Renamed from ext4dev to ext4 in kernel 2.6.28). ▐ Maintainers Theodore Ts'o [email protected] , Andreas Dilger [email protected] ▐ ML [email protected] ▐ Ext4 Wiki http://ext4.wiki.kernel.org Page 4 Copyright(C) 2010 NEC Software Tohoku, Ltd. All Rights Reserved. Ext4 features Page 5 Copyright(C) 2010 NEC Software Tohoku, Ltd. All Rights Reserved. Ext4 features Bigger file/filesystem size support. Compared to ext3, ext4 is: 8 times larger in file size, 65536 times(!) larger in filesystem size.
    [Show full text]
  • Defragmenting Hard Disk
    NIELIT GORAKHPUR Course Name: O Level (2nd Sem) Subject: Introduction to ICT Resources Topic: Defragmenting Hard Disk Date: 23-04-2020 Defragmenting Hard Disk After some use, if you feel that your drive has started getting slow, DOS or Windows programs and data files take much more time to load, then most probably this could be due to a fragmentation problem. Disk Fragmentation On a disk drive, any information is stored in clustery. When all the clusters of a file are stored in consecutive sectors, then it is not fragmented but when the clusters which make a file are scattered across the disk, the file or the disk is said to be fragmented. As it takes the read/write head longer to read the file scattered across the disk surface, a fragmented file takes longer to load compared to an un-fragmented file. This can be compared with a real life situation. If your room is not in order, it takes you longer to find something compared to a room where everything is arranged properly. The fragmentation occurs because whenever the operating system wants to write some information on the disk drive, it consults the FAT (File Allocation Table) to find an empty cluster. The FAT keeps a record of used, available and bad (unusable) areas on the disk surface. After finding an empty cluster, the operating system writes to that area and updates the FAT. If the complete file could not be written in one contiguous empty area, then the operating system looks for other areas where the rest of the file can be written.
    [Show full text]
  • NTFS/FAT Disk Defragmentation in RAID and SAN Environments
    Defragmentation Technology | White Paper NTFS/FAT Disk Defragmentation in RAID and SAN Environments A detailed look at how defragmentation really works and how it can deliver significant benefits to RAID or SAN/NAS storage. www.raxco.com 2 There is a common misconception that disk defragmentation is not necessary in RAID or SAN/NAS storage environments. This document explains how disk defragmentation really works and how it can deliver significant benefits to RAID or SAN/NAS storage. The idea that disk defragmentation software is not necessary on RAID or SAN storage arises from a misunderstanding of how disk defragmentation software works and how it interacts with the disk controller software in these environments. At the core of this issue is the common perception that disk defragmentation software directly shuffles around disk clusters. That belief is incorrect. The Windows file systems, FAT and NTFS, “know” absolutely nothing about the configuration of the attached storage. They do not know if a disk is IDE, SCSI, RAID, or SAN. The only thing the file system knows is what kind of partition it is, NTFS or FAT, and how big it is. When a disk is formatted, the file system enumerates the drive into logical disk clusters starting with Logical Cluster Number (LCN) zero up to LCN NNNNNNN, depending on the size of the disk. As file space is allocated and deleted, the file system updates its logical map of the LCN’s. When an application requests a file, the file system queries the Master File Table (for NTFS) and obtains the starting LCN and the run length for the file.
    [Show full text]