DOCSLIB.ORG

File System Administration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

File System Administration 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. A Sun Microsystems, Inc. Business 1994 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® and Berkeley 4.3 BSD systems, licensed from UNIX System Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and the University of California, respectively. Third-party font software in this product is protected by copyright and licensed from Sun’s font suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, the Sun logo, Sun Microsystems, Sun Microsystems Computer Corporation, SunSoft, the SunSoft logo, Solaris, SunOS, OpenWindows, DeskSet, ONC, ONC+, and NFS are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and certain other countries. UNIX is a registered trademark of Novell, Inc., in the United States and other countries; X/Open Company, Ltd., is the exclusive licensor of such trademark. OPEN LOOK® is a registered trademark of Novell, Inc. PostScript and Display PostScript are trademarks of Adobe Systems, Inc. Archive is a registered trademark of Archive Corporation. Emulex is a registered trademark of Emulex Corporation. Sysgen is a registered trademark of Systen, Inc. Xylogics is a registered trademark of Xylogics, Inc. All other product names mentioned herein are the trademarks of their respective owners. All SPARC trademarks, including the SCD Compliant Logo, are trademarks or registered trademarks of SPARC International, Inc. SPARCstation, SPARCserver, SPARCengine, SPARCstorage, SPARCware, SPARCcenter, SPARCclassic, SPARCcluster, SPARCdesign, SPARC811, SPARCprinter, UltraSPARC, microSPARC, SPARCworks, and SPARCompiler are licensed exclusively to Sun Microsystems, Inc. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements. X Window System is a product of the Massachusetts Institute of Technology. THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME. Please Recycle Contents Preface. xix Part 1 —Administering File Systems 1. Planning File Systems . 1 Types of File Systems. 2 Disk-Based File Systems . 3 Network-Based File Systems . 3 Pseudo File Systems . 4 File System Administration Commands. 7 Syntax of Generic Commands . 8 Manual Pages for Generic and Specific Commands . 9 How the File System Commands Determine the File System Type. 9 How to Find Out the Type of a File System . 9 The Default SunOS File Systems . 12 Understanding Disk Device Names . 13 Understanding the UFS File System . 13 iii Disk Slices . 14 Cylinder Groups . 19 Planning UFS File Systems . 19 File System Parameters . 20 Making File Systems Available . 21 Understanding Mounting and Unmounting . 22 The Automounter . 29 Sharing Files From a Server . 29 2. Creating File Systems. 35 Creating a UFS File System on a Disk Slice . 35 Preparing to Create a UFS File System . 36 Installing a Boot Block on a UFS File System. 37 Creating a File System on a Diskette . 37 Creating a Temporary File System (TMPFS) . 38 Creating a Loopback File System. 39 3. Mounting and Unmounting File Systems . 41 Finding Out Which File Systems Are Mounted . 41 Creating Entries in the File System Table . 42 Mounting File Systems in the File System Table . 45 Mounting File Systems From the Command Line. 47 Unmounting File Systems. 53 Sharing File Systems . 55 Examples of Automatic Sharing Entries in the /etc/dfs/dfstab File . 56 iv File System Administration—August 1994 4. Copying UFS Files and File Systems. 57 Commands for Copying File Systems. 58 Copying Complete File Systems . 58 Using the labelit and volcopy Commands . 59 Using the dd Command . 63 Using the cpio Command . 64 Copying Files and File Systems to Tape . 65 Useful Commands for Streaming Tape Cartridges . 65 Using the tar Command . 67 Using the cpio Command . 69 Copying Files and File Systems to Diskette . 72 Copying Files with a Different Header Format . 76 Retrieving Files Created With the bar Command. 77 5. The Cache File System . 79 Cache File System Concepts . 79 Resource Management . 80 Front File System Requirements . 80 Setting Up a Cached File System . 80 Administering a Cache . 81 Creating a Cache . 81 Cache Parameters . 81 Setting Cache Parameters . 83 Modifying Parameters. 84 Displaying Information About Cached File Systems . 85 Contents v Deleting Cached File Systems . 86 Mounting a Cached File System. 86 Using mount to Mount a Cached File System . 87 Creating a vfstab Entry for Cached File Systems . 91 Checking a Cached File System . 91 Part 2 —Backup and Restore 6. Planning a Backup Strategy . 95 Why You Back Up File Systems . 95 Understanding the ufsdump Command . 96 Advantages of ufsdump . 96 Disadvantages of ufsdump . 97 How ufsdump Works . 97 Choosing Which File Systems to Back Up . 99 File Systems to Back Up on a Standalone System . 100 File Systems to Back Up on a Server . 100 Choosing Which Media to Use. 102 Backup Device Names. 103 Guidelines for Drive Maintenance and Media Handling. 107 Considering Other Issues . 108 When to Run Backups. 108 How Long to Save Backups . 109 How to Back Up Files to a Remote Drive . 109 Do You Need to Become Superuser?. 110 Should You Check File Systems Before a Full Backup? . 110 vi File System Administration—August 1994 Do You Want to Put Multiple Backups on the Same Tape? 111 Where Do the Files Reside? . 111 How Do You Backup on a Heterogeneous Network? . 111 What Are the Security Issues? . 112 Planning a Backup Schedule . 112 7. Backing Up Files and File Systems . 121 Preparing to Do Backups . 121 Doing Complete Backups . 126 Doing Incremental Backups . 128 Backing Up Individual Files and Directories . 128 Using a Remote Drive to Do Backups . 128 Doing Backups on Remote Systems . 130 Troubleshooting When the Root File System Fills Up. 130 Options and Arguments for the ufsdump Command. 131 Default Command Options . 132 Options for the ufsdump Command. 132 8. Restoring Files and File Systems . 139 Preparing to Restore Files and File Systems. 139 Determining Which Tapes to Use . 140 Determining the Disk Device Name . 141 Determining the Type of Tape Drive You Will Use . 142 Determining the Tape Device Name . 142 Restoring Complete File Systems. 142 Synopsis of Steps ..
Recommended publications
  • Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4

    Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4

    SUSE Linux Enterprise Server 12 SP4 Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4 Provides information about how to manage storage devices on a SUSE Linux Enterprise Server. 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 xii 2 Giving Feedback xiv 3 Documentation Conventions xiv 4 Product Life Cycle and Support xvi Support Statement for SUSE Linux Enterprise Server xvii • Technology Previews xviii I FILE SYSTEMS AND MOUNTING 1 1 Overview
  • File Formats

    File Formats

    man pages section 4: File Formats Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–3945–10 September 2004 Copyright 2004 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
  • Z/OS Distributed File Service Zseries File System Implementation Z/OS V1R13

    Z/OS Distributed File Service Zseries File System Implementation Z/OS V1R13

    Front cover z/OS Distributed File Service zSeries File System Implementation z/OS V1R13 Defining and installing a zSeries file system Performing backup and recovery, sysplex sharing Migrating from HFS to zFS Paul Rogers Robert Hering ibm.com/redbooks International Technical Support Organization z/OS Distributed File Service zSeries File System Implementation z/OS V1R13 October 2012 SG24-6580-05 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. Sixth Edition (October 2012) This edition applies to version 1 release 13 modification 0 of IBM z/OS (product number 5694-A01) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2010, 2012. 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 . xiii Trademarks . xiv Preface . .xv The team who wrote this book . .xv Now you can become a published author, too! . xvi Comments welcome. xvi Stay connected to IBM Redbooks . xvi Chapter 1. zFS file systems . 1 1.1 zSeries File System introduction. 2 1.2 Application programming interfaces . 2 1.3 zFS physical file system . 3 1.4 zFS colony address space . 4 1.5 zFS supports z/OS UNIX ACLs. 4 1.6 zFS file system aggregates. 5 1.6.1 Compatibility mode aggregates. 5 1.6.2 Multifile system aggregates. 6 1.7 Metadata cache. 7 1.8 zFS file system clones . 7 1.8.1 Backup file system . 8 1.9 zFS log files.
  • Configuring and Managing the Network File System

    Configuring and Managing the Network File System

    ch33.fm Page 639 Saturday, April 29, 2000 1:41 AM THIRTY-THREE 33 Configuring and Managing the Network File System LChapter Syllabus The Network File System (NFS) is used to share files and directories over a network. It is an RPC- 33.1 NFS Concepts based system and works in the client-server model. The NFS server makes some of its file sys- 33.2 Configuring an NFS Server tems shareable with other systems on a network. The NFS client mounts shared file systems from 33.3 Configuring an NFS Client the server to its local mount points. Users of the client machines can use NFS-mounted file systems 33.4 NFS Daemons just like the local file systems. NFS support is available on many platforms including personal 33.5 Troubleshooting computers. On UNIX systems, this has become a de facto standard and provides a transparent way for sharing files. When used in combination with NIS, it facilitates users’ logging in from any machine on the network and finding the same environment, home directories, and mailboxes. NFS is used to save disk space in a number of ways. All files that are static in nature can be shared on a network. These files include applica- tion directories under /opt and operating system files under the /usr directory. The files that are 639 ch33.fm Page 640 Saturday, April 29, 2000 1:41 AM 640 Chapter 33 • Configuring and Managing the Network File System shared by individual users are users’ home directories and mail- boxes. The directories that contain configuration files or log files are usually not shared.
  • Files and Processes (Review)

    Files and Processes (Review)

    Files and Processes (review) Files and Processes (review) 1/61 Learning Objectives Files and Processes (review) I Review of files in standard C versus using system call interface for files I Review of buffering concepts I Review of process memory model I Review of bootup sequence in Linux and Microsoft Windows I Review of basic system calls under Linux: fork, exec, wait, exit, sleep, alarm, kill, signal I Review of similar basic system calls under MS Windows 2/61 Files Files and I Recall how we write a file copy program in standard C. Processes (review) #include <stdio.h> FILE *fopen(const char *path, const char *mode); size_t fread(void *ptr, size_t size, size_t nmemb, FILE *stream); size_t fwrite(const void *ptr, size_t size, size_t nmemb, FILE *stream); int fclose(FILE *fp); I We can also use character-based functions such as: #include <stdio.h> int fgetc(FILE *stream); int fputc(int c, FILE *stream); I With either approach, we can write a C program that will work on any operating system as it is in standard C. 3/61 Standard C File Copy Files and Processes (review) I Uses fread and fwrite. I files-processes/stdc-mycp.c 4/61 POSIX/Unix Files Files and Processes (review) I "On a UNIX system, everything is a file; if something is not a file, it is a process." I A directory is just a file containing names of other files. I Programs, services, texts, images, and so forth, are all files. I Input and output devices, and generally all devices, are considered to be files.
  • GPFS Policy Engine

    GPFS Policy Engine

    General Parallel File System Version 4 Release 1 Administration and Programming Reference SA23-1452-00 General Parallel File System Version 4 Release 1 Administration and Programming Reference SA23-1452-00 Note Before using this information and the product it supports, read the information in “Notices” on page 655. This edition applies to version 4 release 1 modification 0 of the following products, and to all subsequent releases and modifications until otherwise indicated in new editions: v IBM General Parallel File System ordered through Passport Advantage® (product number 5725-Q01) v IBM General Parallel File System ordered through AAS/eConfig (product number 5641-GPF) v IBM General Parallel File System ordered through HVEC/Xcel (product number 5641-GP6, 5641-GP7, or 5641-GP8) Significant changes or additions to the text and illustrations are indicated by a vertical line (|) to the left of the change. IBM welcomes your comments; see the topic “How to send your comments” on page xii. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Tables ...............vii Backing up a file system using the mmbackup command ..............34 About this information ........ix Backing up a file system using the GPFS policy engine ...............40 Prerequisite and related information ......x Backing up file system configuration information 40 Conventions used in this information ......xi Using APIs to develop backup applications.
  • The Application of File Identification, Validation, and Characterization Tools in Digital Curation

    The Application of File Identification, Validation, and Characterization Tools in Digital Curation

    THE APPLICATION OF FILE IDENTIFICATION, VALIDATION, AND CHARACTERIZATION TOOLS IN DIGITAL CURATION BY KEVIN MICHAEL FORD THESIS Submitted in partial fulfillment of the requirements for the degree of Master of Science in Library and Information Science in the Graduate College of the University of Illinois at Urbana-Champaign, 2011 Urbana, Illinois Advisers: Research Assistant Professor Melissa Cragin Assistant Professor Jerome McDonough ABSTRACT File format identification, characterization, and validation are considered essential processes for digital preservation and, by extension, long-term data curation. These actions are performed on data objects by humans or computers, in an attempt to identify the type of a given file, derive characterizing information that is specific to the file, and validate that the given file conforms to its type specification. The present research reviews the literature surrounding these digital preservation activities, including their theoretical basis and the publications that accompanied the formal release of tools and services designed in response to their theoretical foundation. It also reports the results from extensive tests designed to evaluate the coverage of some of the software tools developed to perform file format identification, characterization, and validation actions. Tests of these tools demonstrate that more work is needed – particularly in terms of scalable solutions – to address the expanse of digital data to be preserved and curated. The breadth of file types these tools are anticipated to handle is so great as to call into question whether a scalable solution is feasible, and, more broadly, whether such efforts will offer a meaningful return on investment. Also, these tools, which serve to provide a type of baseline reading of a file in a repository, can be easily tricked.
  • Chapter 10: File System

    Chapter 10: File System

    Chapter 10: File System Operating System Concepts – 9th Edition Silberschatz, Galvin and Gagne © 2013 Chapter 10: File System File Concept Access Methods Disk and Directory Structure File-System Mounting File Sharing Protection Operating System Concepts – 9th Edition 11.2 Silberschatz, Galvin and Gagne © 2013 Objectives To explain the function of file systems To describe the interfaces to file systems To discuss file-system design tradeoffs, including access methods, file sharing, file locking, and directory structures To explore file-system protection Operating System Concepts – 9th Edition 11.3 Silberschatz, Galvin and Gagne © 2013 File Concept Contiguous logical address space Types: Data numeric character binary Program Contents defined by file’s creator Many types Consider text file, source file, executable file Operating System Concepts – 9th Edition 11.4 Silberschatz, Galvin and Gagne © 2013 File Structure None - sequence of words, bytes Simple record structure Lines Fixed length Variable length Complex Structures Formatted document Relocatable load file Can simulate last two with first method by inserting appropriate control characters Who decides: Operating system Program Operating System Concepts – 9th Edition 11.5 Silberschatz, Galvin and Gagne © 2013 File Attributes Name – only information kept in human-readable form Identifier – unique tag (number) identifies file within file system Type – needed for systems that support different types Location – pointer to file location on device Size
  • Man Pages Section 2 System Calls

    Man Pages Section 2 System Calls

    man pages section 2: System Calls Part No: E29032 October 2012 Copyright © 1993, 2012, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including anyoperating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications.
  • Managing Network File Systems in Oracle® Solaris 11.4

    Managing Network File Systems in Oracle® Solaris 11.4

    Managing Network File Systems in ® Oracle Solaris 11.4 Part No: E61004 August 2021 Managing Network File Systems in Oracle Solaris 11.4 Part No: E61004 Copyright © 2002, 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.
  • Wikipedia: Design of the FAT File System

    Wikipedia: Design of the FAT File System

    Design of the FAT file system A FAT file system is a specific type of computer file system architecture and FAT a family of industry-standard file systems utilizing it. Developer(s) Microsoft, SCP, IBM, [3] The FAT file system is a legacy file system which is simple and robust. It Compaq, Digital offers good performance even in very light-weight implementations, but Research, Novell, cannot deliver the same performance, reliability and scalability as some Caldera modern file systems. It is, however, supported for compatibility reasons by Full name File Allocation Table: nearly all currently developed operating systems for personal computers and FAT12 (12- many home computers, mobile devices and embedded systems, and thus is a bit version), well suited format for data exchange between computers and devices of almost FAT16 (16- any type and age from 1981 through the present. bit versions), Originally designed in 1977 for use on floppy disks, FAT was soon adapted and FAT32 (32-bit version used almost universally on hard disks throughout the DOS and Windows 9x with 28 bits used), eras for two decades. Today, FAT file systems are still commonly found on exFAT (64- floppy disks, USB sticks, flash and other solid-state memory cards and bit versions) modules, and many portable and embedded devices. DCF implements FAT as Introduced 1977 (Standalone the standard file system for digital cameras since 1998.[4] FAT is also utilized Disk BASIC-80) for the EFI system partition (partition type 0xEF) in the boot stage of EFI- FAT12: August 1980 compliant computers. (SCP QDOS) FAT16: August 1984 For floppy disks, FAT has been standardized as ECMA-107[5] and (IBM PC DOS 3.0) ISO/IEC 9293:1994[6] (superseding ISO 9293:1987[7]).
  • C12) United States Patent (10) Patent No.: US 7,418,439 B2 Wong (45) Date of Patent: Aug

    C12) United States Patent (10) Patent No.: US 7,418,439 B2 Wong (45) Date of Patent: Aug

    111111 1111111111111111111111111111111111111111111111111111111111111 US007418439B2 c12) United States Patent (10) Patent No.: US 7,418,439 B2 Wong (45) Date of Patent: Aug. 26, 2008 (54) MIRROR FILE SYSTEM 5,870,734 A * 2/1999 Kao .............................. 707/2 5,873,085 A * 2/1999 Enoki eta!. ................... 707/10 (75) Inventor: John P. Wong, Fremont, CA (US) 5,946,685 A * 8/1999 Cramer eta!. ................ 707/10 6,000,020 A * 12/1999 Chin eta!. .................. 7111162 (73) Assignee: Twin Peaks Software, Inc., Fremont, 6,115,741 A * 9/2000 Domenikos et al .......... 709/217 CA (US) 6,192,408 B1 * 212001 Vahalia eta!. .............. 709/229 6,216,140 B1 * 4/2001 Kramer ...................... 715/511 6,298,390 B1 * 10/2001 Matena eta!. .............. 719/315 ( *) Notice: Subject to any disclaimer, the term of this 6,366,988 B1 * 4/2002 Skiba eta!. ................. 7111165 patent is extended or adjusted under 35 6,466,978 B1 * 10/2002 Mukherjee et al ........... 709/225 U.S.C. 154(b) by 1179 days. 6,625,750 B1 * 9/2003 Duso eta!. .................... 714/11 6,697,846 B1 * 2/2004 Soltis ......................... 709/217 (21) Appl. No.: 09/810,246 OTHER PUBLICATIONS (22) Filed: Mar. 19, 2001 Veritas User Manual, File Replicator™ 3 .0.1 for Solaris®, Jan. 2001, (65) Prior Publication Data pp. 1-115. US 2001/0051955 Al Dec. 13, 2001 * cited by examiner Primary Examiner-Sana Al-Hashemi Related U.S. Application Data (74) Attorney, Agent, or Firm-Buchanan Ingersoll & (60) Provisional application No. 60/189,979, filed on Mar. Rooney PC 17,2000. (57) ABSTRACT (51) Int.