1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. Open Enterprise Server 2
  6. System administration manual

Novell Open Enterprise Server 2 System Administration Manual

Netware traditional file system
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Novell
Open Enterprise Server
2
S e p t e m b e r 2 0 0 7
®
N E T W A R E
T R A D I T I O N A L F I L E
S Y S T E M A D M I N I S T R A T I O N G U I D E
w w w . n o v e l l . c o m

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Open Enterprise Server 2 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell Open Enterprise Server 2

Summary of Contents for Novell Open Enterprise Server 2

  • Page 1 OES 2: NetWare Traditional File System Administration Guide Novell Open Enterprise Server w w w . n o v e l l . c o m ® N E T W A R E T R A D I T I O N A L F I L E...

  • Page 2: Legal Notices

    Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
  • Page 3 Novell Trademarks For a list of Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/ legal/trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.

  • Page 5: Table Of Contents

    Using Novell Remote Manager for NetWare ........
  • Page 6 4.1.5 Suspending File Compression ......... . 32 Salvaging and Purging Files .
  • Page 7 Resolving Volume Mounting Problems Caused by the Name Space Module ... . . 55 Contents...
  • Page 8 OES 2: NetWare Traditional File System Administration Guide...

  • Page 9: About This Guide

    Traditional File System for ® Novell Open Enterprise Server 2 NetWare and NetWare 6.5 SP7. The guide is divided into the following sections: Chapter 1, “Overview of the NetWare Traditional File System,” on page 11 Chapter 2, “Using NetWare Traditional Volumes in a Virtual Guest Server Environment,” on page 15 Chapter 3, “Configuring and Managing NetWare Traditional Volumes,”...
  • Page 10 ® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux* or UNIX*, should use forward slashes as required by your software.

  • Page 11: Overview Of The Netware Traditional File System

    During installation of OES NetWare, your system volume is automatically created as an NSS volume. After installation, you can use Novell Remote Manager for NetWare to create a new Traditional volume on any disk that has a NetWare partition. For information, see the...

  • Page 12: What Happens When You Mount A Traditional Volume

    1.1.2 Traditional Volume Objects in eDirectory In Novell eDirectory , each Traditional volume is represented by a Volume object. Volume objects are leaf objects that represent a physical volume or logical volume on the network.

  • Page 13: What's Next

    A single disk can contain volume segments from multiple volumes. If a single disk fails, each volume segment on it fails, causing all of the volumes that have volume segments on that server disk to fail. To achieve fault tolerance, you should protect the volumes against disk failure by setting up a software RAID 1 (mirroring) device for the partitions.
  • Page 14 OES 2: NetWare Traditional File System Administration Guide...

  • Page 15: Using Netware Traditional Volumes In A Virtual Guest Server Environment

    NetWare Traditional volumes can be used on NetWare guest servers in a virtualized environment ® just as they are on physical NetWare servers. Novell Storage Services (NSS) is responsible for managing virtual devices for the virtual machine, which parallels the NSS role for storage management on physical servers.

  • Page 16: Section 7.1.3, "For 16-Bit Disk Adapters, Increase The Number Of Reserved Buffers Below

    OES 2: NetWare Traditional File System Administration Guide...

  • Page 17: Configuring And Managing Netware Traditional Volumes

    Guide. This section discusses the following file and directory management tasks: Section 3.1, “Using Novell Remote Manager for NetWare,” on page 17 Section 3.2, “Managing NetWare Partitions for Traditional Volumes,” on page 18 Section 3.3, “Creating a NetWare Partition for Traditional Volumes,” on page 19 Section 3.4, “Expanding the Size of a NetWare Partition,”...

  • Page 18: Managing Netware Partitions For Traditional Volumes

    Traditional volumes, and free space at different levels of indentation. Depending on what tasks can be performed on the listed storage item, Novell Remote Manager for NetWare displays task-based links next to the devices, Traditional volumes, and free space: Create: Create a new volume on the selected device.

  • Page 19: Creating A Netware Partition For Traditional Volumes

    The maximum supported partition size for Traditional NetWare partitions is 4 GB. 1 In Novell Remote Manager for NetWare, click Manage Server > Partition Disks. 2 Locate the device that you want to create the partition on, then click the Create link next to it.

  • Page 20: Deleting A Netware Partition

    Before you can delete a mirrored partition, unmirror the partition, then delete it. Unmirror a Partition 1 In Novell Remote Manager for NetWare, click Manager Servers > Partition Disks. 2 Locate and the partition you want to unmirror, then click the Remove Mirror link next to it.

  • Page 21: Mounting A Traditional Volume

    To increase the size of a Traditional volume, add another segment to that volume. 1 In Novell Remote Manager for NetWare, Click Manage Server > Partition Disks. 2 Locate the volume you want to expand, then click the Expand link next to it.

  • Page 22: Setting The Space Quota For A Traditional Volume

    3.11 Setting the Space Quota for a Traditional Volume 1 In Novell Remote Manager for NetWare, click Manage Servers > Volumes. 2 Locate the volume you want to set quotas for, then click the Space Quota link next to it.

  • Page 23: Calculating Memory Required For Name Space Support

    If you have insufficient memory to mount a Traditional volume with a long name space, you might want to convert the volume to an NSS volume. For information, see “Upgrading Legacy NSS and NetWare Traditional Volumes” in the OES 2: NSS File System Administration Guide.

  • Page 24: Removing Name Spaces

    3 Click Delete Partition Label, then click OK. 3.17 Deleting a Traditional Volume 1 In Novell Remote Manager, click Manager Servers > Volumes to view a list of volumes. 2 Locate the Traditional volume you want to delete, then click the Delete link next to it.

  • Page 25: Prerequisites

    Dismount the volume (see Section 3.9, “Dismounting a Traditional Volume,” on page 21), then use the Vrepair utility to correct volume problems or to remove name space entries from File Allocation Tables (FATs) and Directory Entry Tables (DETs). You can run the Vrepair utility (vrepair) on a damaged volume while other volumes are mounted. For details about using the Vrepair utility, see “VREPAIR”...

  • Page 26: Protecting Data: Disk Mirroring And Duplexing

    Repeat until the Vrepair utility finds no errors. If you are unable to mount the volume after running the Vrepair utility several times, you must delete the volume, then re-create the volume using Novell Remote Manager for NetWare. 3.19 Protecting Data: Disk Mirroring and Duplexing NetWare allows you to protect your data with disk mirroring or duplexing.

  • Page 27: Upgrading Media Format From Traditional Volumes To Nss Volumes

    word processor and rename the directory, you need to change the mapping in every login script where that search mapping appears. By using a Directory Map object, you could avoid making changes to the login scripts. ® First, using ConsoleOne , you could create a Directory Map object called current_wpr that points to the word processor directory (sys:\public\wpr\80).
  • Page 28 OES 2: NetWare Traditional File System Administration Guide...

  • Page 29: Configuring Advanced Features For Traditional Volumes

    Configuring Advanced Features for Traditional Volumes ® This section discusses how to optimize file system performance for your NetWare Traditional File System storage and file management systems. Section 4.1, “Compressing and Decompressing Files,” on page 29 Section 4.2, “Salvaging and Purging Files,” on page 32 4.1 Compressing and Decompressing Files One way to conserve disk space is to compress files.

  • Page 30: Setting Server-Level File Compression Attributes

    If you flag an item for immediate compression during peak system usage, performance might deteriorate. Files Remain Compressed during Backup and Restore Backup applications that use Novell Storage Management Services (SMS ) can back up and restore files in their compressed state. Other applications might decompress them.

  • Page 31: Enabling File Compression For A Traditional Volume

    Minimum Compression Percentage Gain Enable File Compression Maximum Concurrent Compressions Convert Compressed to Uncompressed Option Decompress Percent Disk Space Free To Allow Commit Decompress Free Space Warning Interval Deleted Files Compression Option Days Untouched Before Compression 4.1.3 Enabling File Compression for a Traditional Volume You choose to compress files when you create volumes by setting the File Compression attribute.You can also set the File Compression attribute later.

  • Page 32: Suspending File Compression

    4.1.5 Suspending File Compression Use the set command’s Enable File Compression parameter to temporarily suspend file compression for a volume. For instructions, see “SET” in the OES 2: Utilities Reference. While file compression is suspended, files that would have been compressed are queued and compressed when compression is re-enabled.

  • Page 33: Purging Deleted Files

    You can view a list of deleted files in a directory and recover files by using Novell Remote Manager for NetWare. For more information on salvaging files, see the OES 2: Novell Remote Manager for NetWare Administration Guide. Recovered files contain information about who deleted the files and when they were deleted.
  • Page 34 OES 2: NetWare Traditional File System Administration Guide...

  • Page 35: Using Software Raid1 Devices For Data Fault Tolerance

    Using Software RAID1 Devices for Data Fault Tolerance ® NetWare Traditional File System volumes can span multiple disks. If a single disk fails, all Traditional volumes that have segments on that disk also fail. To increase the data fault tolerance of a server that has a Traditional file system, you can mirror the data from a Traditional NetWare partition on one disk to Traditional NetWare partitions on other disks.

  • Page 36: Key Concepts For Mirroring Traditional Netware Partitions

    Duplexing is the recommended method for fault tolerance because two channels rarely fail simultaneously. The process for mirroring and duplexing is the same. The term mirroring is used in all menus in Novell Remote Manager for NetWare to refer to both mirroring and duplexing. OES 2: NetWare Traditional File System Administration Guide...

  • Page 37: Example Software Raid1 Solution For Fault Tolerance Of Traditional Volumes

    You set the Mirror attribute for a partition when you create it. 1 In Novell Remote Manager for NetWare, click Manage Server > Partition Disks. 2 Locate the device that you want to create the partition on, then click Create.

  • Page 38: Unmirroring Partitions

    You must unmirror mirrored partitions before you can delete a partition or conduct surface tests on a disk. 1 In Novell Remote Manager for NetWare, click Manager Servers > Partition Disks. 2 Locate the partition you want to unmirror, then click the Remove Mirror link next to it.
  • Page 39 This initiates the resynchronization process for the mirror group that contains the partition you selected. 2 Check the mirror status to confirm the resynchronization. Using Software RAID1 Devices for Data Fault Tolerance...
  • Page 40 OES 2: NetWare Traditional File System Administration Guide...

  • Page 41: Using Software Raid0 Devices To Enhance Disk I/O Performance

    Using Software RAID0 Devices to Enhance Disk I/O Performance If your disk response time is slow for heavily used volumes, you can improve disk I/O performance ® by using a software RAID0 device for the volume. Even though the NetWare Traditional File System volumes can comprise segments from multiple disks, the disks are not forced to distribute data evenly across the member disks.

  • Page 42: Managing Traditional Software Raid0 Devices

    OES 2: NSS File System Administration Guide. After you create the RAID0, use Novell Remote Manager for NetWare to create a Traditional volume on the device. Make sure to use the RAID0 for your segment. For information on creating a Traditional volume, see Section 3.7, “Creating and Mounting a Traditional Volume,”...

  • Page 43: Optimizing Disk And Cache Performance For Traditional Volumes

    Section 7.5, “Configuring Common File System SET Parameters for NetWare,” on page 49 For instructions on using the set command, see “SET” in the OES 2: Utilities Reference. For instructions on configuring set command parameters in Novell Remote Manager for NetWare, see the OES 2: Novell Remote Manager for NetWare Administration Guide.

  • Page 44: Disable Read-After-Write-Verify

    Keep at least 1000 free blocks on each Traditional volume that has suballocation enabled. Free blocks are disk blocks that have no files stored in them. If the number of free blocks is low, the suballocation increases server utilization. To view the number of free blocks, view the volume’s details in iManager.

  • Page 45: Improving Disk Reads On Traditional Volumes

    WARNING: Do not fill up your sys: volume. This could damage your entire file system. The Transaction Tracking System , which protects Novell eDirectory , shuts down, compromising the eDirectory replicas on the server. To keep enough free space on volumes, try the following suggestions: Regularly monitor each volume’s disk space.

  • Page 46: Change The Turbo Fat Wait Time For Faster Reads Of Traditional Volumes

    7.2.2 Change the Turbo FAT Wait Time for Faster Reads of Traditional Volumes When a program randomly accesses a file that contains more than 64 file allocation table (FAT) entries, the file system builds a turbo FAT index for the file so that the information in the file can be accessed quickly.

  • Page 47: Change Disk And Directory Caching For Faster Writes

    7.3.2 Change Disk and Directory Caching for Faster Writes Change the Disk and Directory Caching parameter for faster writes if network users frequently make many small write requests and the server is slow to respond to the requests. Use “SET” in the OES 2: Utilities Reference to modify the following parameters: Increase the value of the Dirty Disk Cache Delay Time parameter.

  • Page 48: Configuring Set Parameters For The Netware Traditional File System

    Procedure Use the “SET” command as described in the OES 2: Utilities Reference to disable the Disk Read After Write Verification parameter. 7.4 Configuring SET Parameters for the NetWare Traditional File System Table 7-1 indicates the default settings in NetWare 6.5 or later for the Traditional file system SET parameters.

  • Page 49: Configuring Common File System Set Parameters For Netware

    SET Parameters for the Traditional File System Default Value Dirty Disk Cache Delay Time 3.3 seconds Minimum File Cache Report Threshold Automatically Repair Bad Volumes File Delete Wait Time 5 minutes 29.6 seconds Allow Deletion Of Active Directories Maximum Percent of Volume Space Allowed for Extended Attributes Maximum Extended Attributes per File or Path Purge Files On Dismount Fast Volume Mounts...
  • Page 50 Common File System SET Parameters Default Value Compression Daily Check Starting Hour Minimum Compression Percentage Gain Enable File Compression Maximum Concurrent Compressions Convert Compressed To Uncompressed Option Decompress Percent Disk Space Free To Allow Commit [XXX] Decompress Free Space Warning Interval 31 minutes 18.5 seconds Deleted Files Compression Option Days Untouched Before Compression...

  • Page 51: Troubleshooting

    Troubleshooting This section presents various troubleshooting procedures for resolving problems with Traditional volumes: Section 8.1, “Resolving File I/O Errors,” on page 51 Section 8.2, “Resolving Volume I/O Errors,” on page 51 Section 8.3, “Resolving Problems When the Server Hangs after Mounting the Last Volume,” on page 52 Section 8.4, “Resolving Problems When No Volumes Mount,”...

  • Page 52: Resolving Problems When The Server Hangs After Mounting The Last Volume

    The sys: volume contains the NetWare system files and the NLM programs. If the sys: volume does not mount when the server is booted, then the autoexec.ncf file does not execute, LAN drivers do not load, and the volume does not become part of the Novell eDirectory tree.

  • Page 53: Resolving Problems When Only Some Volumes Mount

    8.5 Resolving Problems When Only Some Volumes Mount To diagnose problems when only some volumes mount, identify whether the following conditions exist: The server does not have enough RAM. The disk drivers for external drives are not loaded. To resolve problems when only some volumes mount, do the following: Add more RAM.

  • Page 54: Resolving Volume Mounting Problems Caused By Corrupted Directory Entry Tables Or File Allocation Tables

    To resolve memory errors when a volume mounts, perform the following actions or ensure that the following conditions exist: Check the status of the available cache buffers. If the cache buffers are fewer than 20%, add more RAM to your server. Free up memory by unloading resources.

  • Page 55: Section 8.9, "Resolving Volume Mounting Problems Caused By The Name Space Module

    8.9 Resolving Volume Mounting Problems Caused by the Name Space Module After a volume has been configured to support more than the DOS naming convention, the name space NLM program must be loaded before the volume can be mounted. To diagnose problems when a Traditional volume cannot mount because the name space NLM program is not loaded, identify whether the following conditions exist: The command to load the name space NLM is not in the startup.ncf file.

Table of Contents