OES 2: NetWare Traditional File System Administration Guide
Novell
Open Enterprise Server
novdocx (en) 6 April 2007
2
September 2007
www.novell.com
NETWARE® TRADITIONAL FILE
SYSTEM ADMINISTRATION GUIDE
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. 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.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
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.
novdocx (en) 6 April 2007
novdocx (en) 6 April 2007
Contents
About This Guide9
1 Overview of the NetWare Traditional File System11
6OES 2: NetWare Traditional File System Administration Guide
8.9Resolving Volume Mounting Problems Caused by the Name Space Module . . . . . . . . . . . . . 55
novdocx (en) 6 April 2007
Contents7
novdocx (en) 6 April 2007
8OES 2: NetWare Traditional File System Administration Guide
About This Guide
This guide discusses how to configure and manage the NetWare® Traditional File System for
®
Novell
following sections:
Open Enterprise Server 2 NetWare and NetWare 6.5 SP7. The guide is divided into the
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,” on page 17
Chapter 4, “Configuring Advanced Features for Traditional Volumes,” on page 29
Chapter 5, “Using Software RAID1 Devices for Data Fault Tolerance,” on page 35
Chapter 6, “Using Software RAID0 Devices to Enhance Disk I/O Performance,” on page 41
Chapter 7, “Optimizing Disk and Cache Performance for Traditional Volumes,” on page 43
Chapter 8, “Troubleshooting,” on page 51
novdocx (en) 6 April 2007
Audience
This guide is intended for system administrators of a NetWare server that uses NetWare Traditional
file systems.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comment feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of the NetWare Traditional File System Administration Guide for OES,
see the OES Documentation Web Site (http://www.novell.com/documentation/oes2/index.html).
Additional Documentation
For more information, see the following:
OES 2: NetWare Server Disks and Storage Devices
OES 2: File Systems Management Guide
OES 2: NSS File System Administration Guide
OES 2: Novell Remote Manager for NetWare Administration Guide
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
About This Guide
9
A trademark symbol (®, TM, 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.
novdocx (en) 6 April 2007
10OES 2: NetWare Traditional File System Administration Guide
1
Overview of the NetWare
novdocx (en) 6 April 2007
Traditional File System
The NetWare® Traditional File System provides legacy storage and file system management for
®
Novell
The Novell Storage ServicesTM File System (NSS) provides the primary system for storage and file
management for NetWare. The NetWare operating system and its extensions are installed on an NSS
pool and volume, named sys. For information, see “Comparison of NSS on NetWare and the
NetWare Traditional File System” in the OES 2: NSS File System Administration Guide.
IMPORTANT: You can optionally use the Traditional volumes on the same server with your NSS
volumes. However, if you are planning to implement Apple* File Protocol (AFP), Network File
System (NFS), or Common Internet File System (CIFS) for this server, you must use the NSS file
system, not the Traditional file system for your system volume and for any data volumes that use
these protocols. For information, see OES 2: Native File Access Protocols Guide.
To upgrade your Traditional volumes to NSS volumes, see “Upgrading Legacy NSS and NetWare
Traditional Volumes” in the OES 2: NSS File System Administration Guide.
This section discusses the following key concepts:
Open Enterprise Server NetWare.
Section 1.1, “NetWare Traditional Volumes,” on page 11
1
Section 1.2, “Traditional Volume Segments,” on page 12
Section 1.3, “What’s Next,” on page 13
1.1 NetWare Traditional Volumes
Traditional volumes consist of a fixed amount of physical space on one or more server disks. A
NetWare server supports up to 255 volumes of any combination of Traditional and NSS volumes,
plus the system volume.
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 OES 2: Novell
Remote Manager for NetWare Administration Guide.
You subdivide Traditional volumes in two ways:
Physically: Traditional volumes consist of physical partitions called volume segments. If a
Traditional volume contains multiple volume segments, its member segments can reside on
multiple server disks. For information about volume segments, see Section 1.2, “Traditional
Volume Segments,” on page 12.
Logically: You divide volumes into directories. In turn, the directories contain files and
subdirectories created by network supervisors and users who have the appropriate rights. For
information about directories and subdirectories, see “Understanding NetWare Directory
Structures” the OES 2: File Systems Management Guide.
Overview of the NetWare Traditional File System
11
1.1.1 What Happens When You Mount a Traditional Volume
When you boot a NetWare server, each Traditional volume is mounted, meaning the following:
The volume becomes visible to the operating system.
The volume’s File Allocation Table (FAT) is loaded into memory.
A single block of data in the file takes up one entry in the FAT. Because of this, volumes with a
smaller block size require more server memory to mount and manage, and it takes longer to
mount the volume. However, if most of your files are small, a large block size wastes disk
space.
The volume’s directory entry table (DET) is loaded into the server memory.
As the Traditional volume is mounted, the FAT and DET fill cache buffers in the server memory.
The more files and directories in the volume, the longer it takes to mount. If a Traditional volume
fails to mount, it might be because you have run out of server memory.
1.1.2 Traditional Volume Objects in eDirectory
novdocx (en) 6 April 2007
In Novell eDirectoryTM, 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.
The Volume object’s properties contains the following information:
The NetWare server the physical volume resides on
The volume name recorded when the volume was initialized on the server (for example, sys:)
The volume’s owner
Space use restrictions for users
A description of the volume’s use
Statistical information on disk space availability, block size, directory entries, name space
support, and so on.
1.2 Traditional Volume Segments
A Traditional volume can use space from up to 32 logical or physical devices. The volume can grow
up to 1 TB in total size for all segments combined. Each segment of space is taken from a NetWare
partition. The segments of space are automatically carved by the management tools when you create
the volume.
The advantage of distributing a volume’s segments across multiple server disks is that different parts
of the same volume can be read from or written to concurrently, which speeds up disk I/O.
Because of hardware restrictions, a hard drive can contain up to four NetWare partitions, or three
NetWare partitions and one DOS partition. (The hard drive that contains the sys: volume also
contains a DOS partition.)
Each NetWare partition can contain up to eight Traditional volume segments. Thus, a single server
disk can contain up to 32 volume segments (4 NetWare partitions with 8 segments each). A single
NetWare partition can contain up to eight Traditional NetWare volumes, each with a single volume
segment.
12OES 2: NetWare Traditional File System Administration Guide
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. See “Using Software RAID1 Devices for
Data Fault Tolerance” on page 35.
You can add volume segments to a Traditional volume if free space is available, but you cannot
remove them. Removing a segment from a volume destroys the entire volume.
You can increase the size of a Traditional volume by adding another server disk to the NetWare
server, setting up a NetWare partition on the disk, then adding one or more segments in the partition
to the existing volume.
1.3 What’s Next
Use the table below to determine where next to go in this document.
Tas kRe ference
novdocx (en) 6 April 2007
Configure and manage Traditional NetWare
partitions and volumes
Optimize storage performanceChapter 4, “Configuring Advanced Features for
Create a software RAID deviceChapter 5, “Using Software RAID1 Devices for
Troubleshoot problemsChapter 8, “Troubleshooting,” on page 51
Plan your directory structure“Planning Directory Structures for NetWare” in the
Create and manage directories and files, including
purging and salvaging (undeleting) deleted files
Configure file system trustees, trustee rights,
inherited rights filters, and attributes for directories
and files
Chapter 3, “Configuring and Managing NetWare
Traditional Volumes,” on page 17
Traditional Volumes,” on page 29
Data Fault Tolerance,” on page 35
Chapter 6, “Using Software RAID0 Devices to
Enhance Disk I/O Performance,” on page 41
OES 2: File Systems Management Guide.
“Configuring Directories for NetWare and NSS on
Linux” in the OES 2: File Systems Management
Guide.
“Configuring File System Trustees, Trustee Rights,
Inherited Rights Filters, and Attributes” in the OES
2: File Systems Management Guide.
Overview of the NetWare Traditional File System13
novdocx (en) 6 April 2007
14OES 2: NetWare Traditional File System Administration Guide
2
Using NetWare Traditional
novdocx (en) 6 April 2007
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
managing virtual devices for the virtual machine, which parallels the NSS role for storage
management on physical servers. For information, see “Using NSS in a Virtual Guest Server
Environment” in the OES 2: NSS File System Administration Guide.
For information about using Xen* virtual environments on an OES 2 Linux virtual host server, see
“Introduction to Xen Virtualization” in the Virtualization: Getting Started guide.
For information on setting up a NetWare virtualized guest server on the host server, see “Setting Up
Virtual Machines” in the Virtualization: Getting Started guide and “NetWare Virtual Machines” in
the Virtualization: Guest Operating System Guide.
®
Storage ServicesTM (NSS) is responsible for
2
Using NetWare Traditional Volumes in a Virtual Guest Server Environment
15
novdocx (en) 6 April 2007
16OES 2: NetWare Traditional File System Administration Guide
3
Configuring and Managing
novdocx (en) 6 April 2007
NetWare Traditional Volumes
You manage the NetWare® Traditional File System volumes with Novell® Remote Manager for
NetWare. For information about this management tool, see OES 2: Novell Remote Manager for
NetWare Administration 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,” on page 19
Section 3.5, “Unmirroring a Mirrored NetWare Partition,” on page 19
Section 3.6, “Deleting a NetWare Partition,” on page 20
Section 3.7, “Creating and Mounting a Traditional Volume,” on page 20
Section 3.8, “Mounting a Traditional Volume,” on page 21
Section 3.9, “Dismounting a Traditional Volume,” on page 21
Section 3.10, “Expanding the Size of a Traditional Volume,” on page 21
Section 3.11, “Setting the Space Quota for a Traditional Volume,” on page 22
3
Section 3.12, “Salvaging and Purging Files,” on page 22
Section 3.13, “Loading and Installing Name Spaces on a Traditional Volume,” on page 22
Section 3.14, “Storing Non-DOS Files on a Traditional Volume,” on page 22
Section 3.15, “Creating an eDirectory Object for a Traditional Volume,” on page 24
Section 3.16, “Naming or Renaming a Traditional NetWare Partition or Volume,” on page 24
Section 3.17, “Deleting a Traditional Volume,” on page 24
Section 3.18, “Repairing a Traditional Volume,” on page 24
Section 3.19, “Protecting Data: Disk Mirroring and Duplexing,” on page 26
Section 3.20, “Using Directory Map Objects,” on page 26
Section 3.21, “Upgrading Media Format from Traditional Volumes to NSS Volumes,” on
page 27
3.1 Using Novell Remote Manager for NetWare
To access Novell Remote Manager for NetWare:
1 Open a Web browser, then go to the following URL to open the login page.
https://server-ip-address:8009
Replace server-ip-address with the IP address (such as 192.168.1.1) or DNS name (such as
servername.example.com) of the server you want to manage.
Configuring and Managing NetWare Traditional Volumes
17
Loading...
+ 38 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.