After you upgrade to NetWare® 6 and reboot the server, you need to update your NSS volumes. NSS volumes from previous releases will not function until you update them to NetWare 6 volumes-they do not upgrade automatically.
Checking the NDS Status
Before you update NSS volumes, you must ensure that NDS® is running properly; otherwise, the upgrade process might remove your trustees. To check ensure NDS is running, you need to check the time stamp for the backlink process.
Do the following to ensure NDS is running:
Use iMonitor to determine that the upgrade process is complete.
Open iMonitor in a network browser by entering the IP address of the server followed by /nds. For example: http://155.555.1/nds.
Click Agent Process Status > External Reference Status.
Make sure the time stamp (under the Time column) shows a time after the time you began the upgrade-specifically when NDS unloaded during the upgrade. The following graphic provides and example of the time stamp:
If the time stamp shows a time earlier than when you began the upgrade, the backlink process is not complete. Repeat Step 1.a through Step 1.a until the backlink is complete.
Upgrading NSS Volumes
To upgrade NSS volumes, enter one of the following commands at the NetWare 6 server console:
NSS /ZLSSVOLUMEUPGRADE=ALL
NSS /ZLSSVOLUMEUPGRADE=volumename
Using Multipath Support
When you use the server console to assign multiple paths, you can also assign a priority level to each path, according to your preference of which paths you want used first and last. The lower the number, the higher the priority. This number determines which path to take; if the current path fails, the path with the next highest priority is used. Multiple paths can have the same priority level. These values are persistent and they are stored in the registry.
The following commands are available from the server console.
List Failover Devices
This command lists all of the failover devices. It also lists all the paths associated with each device, their assigned priorities, and the path that is selected.
If you want to see the paths associated with one particular device, enter the above command followed by the device ID. For example, if you wanted to see the paths associated with device Ox12, you would enter List Failover Devices Ox12 at the server console and see the following results:
Ox12 [V132-A1-D2:20] ABC DEVICE rev:5678
Up Ox11 [V132-A1-D2:20] ABC DEVICE rev:5678 Priority = 1 selected
Up Ox26 [V132-A1-D2:20] ABC DEVICE rev:5678 Priority = 2
This information tells you that there are two paths assigned to device Ox12. Out of those two devices, number 11 is Up, and it is has also been assigned 1st priority. The word Up, simply means that this path is available for use. The word selected, means that any disk requests that are trying to reach the Ox12 device automatically goes through the number 11 path, unless another path is selected by using the MM Set Failover Path command.
MM Set Failover Priority pathid = number
This command sets the priority level for each path. The pathid must be a valid path ID and the number is a decimal number between 1 and 4 million.
MM Set Failover Priority pathid = number /insert
The /insert option inserts a new path with the specified priority. For example, if you have four existing paths that are assigned the priorities of 1, 2, 3, and 4, and you enter a new path followed by a number 2 and the /insert option, then the paths that were previously assigned to 2, 3, and 4 priority are bumped to priority 3, 4, and 5 in order to accommodate the new path that has been assigned priority 2.
MM Set Failover State pathid = Up /setpath
This command sets the state of the path to Up. The pathid must be a valid path ID. If the path is up, it can be taken down, meaning, it will not be used and another path will be selected. If the Up option is followed by the /setpath option, the highest priority path is automatically selected from the paths that are currently up.
MM Set Failover State pathid = Down /setpath
This command option is useful if you want to do preventative maintenance or reroute cables on good, functional path. If the path is bad, NSS automatically moves the path to a down status.
If the Down option is followed by the /setpath option, the highest priority path is automatically selected from the paths that are currently up.
MM Set Failover Path pathid
This command will mark the path you entered as selected. The pathid must be a valid path that is up. The priority of a path remains static regardless of whether a path is considered up or down.
For more information about selected paths, see the List Failover Devices command of this bulleted list.
MM Restore Failover Pathdeviceid
This command causes the device to reselect the highest priority path that is online. The deviceid must be a valid device ID.
MM Set Multi-path Support = Off
This command will disable multipath support. Using this command, you can turn the multipath support on or off. In order for this command to work, you must put this set parameter in the STARTUP.NCF file before any drivers are loaded.
Transaction Tracking System (TTS)
Transaction Tracking protects database applications by backing out transactions that are incomplete due to a system failure. TTS can be available on either all traditional or all NSS logical volumes. It cannot be available on all volumes if you use both types of volumes. If your system uses both traditional and logical volumes, by default it can only work on traditional volumes. If you want to use it on logical volumes on a system that has both, you must enter DISABLE TTS on the AUTOEXEC.NCF then enable the feature on each logical volume you want it on. Unlike traditional volumes, TTS does not apply to logical volumes by default. To enable it on logical volumes, enter the following command at the server console:
nss/transaction=<volname>.
Setting the Cache Buffers
A cache buffer is a block (4 Kb) of NetWare server memory (RAM) that temporarily stores data. When you install NSS, it consumes 60 percent of the the cache buffers by default.
The following are options for changing the cache buffers:
You can set a maximum of 1048576 cache buffers.
You can set the buffers in percentages rather than integers.
Use the following commands at the server console to set your cache buffers or tune your cache parameters. You can set or tune cache buffers at anytime.
Task
Purpose
Command
Set number of cache buffers
This sets the minimum number of cache buffers allocated for NSS file system access. The default and minimum number of cache buffers is 512. The range is 256 to 1048576.
nss /MinBufferCacheSize=value
Look up cache buffers
To quickly look up cache buffers, the cache uses a hashing algorithm that maps names to buckets. Sometimes multiple names map to the same bucket. When this occurs, all names must be searched to determine if the entry is in the cache. The number of entries in the hash table is proportional to the amount of free memory available when you load NSS.
nss /NumHashBuckets
Set cache buffers for traditional file system
You can set the minimum number of cache buffers that NSS allocates for traditional file system access. To accomplish this, NSS returns pages to the operating system. This occurs until the operating system has enough pages, or until NSS reaches the minimum number of pages. The default is 1024. The range is 1024 to 1048576.
nss /MinOSBufferCacheSize
Set the cache for file and directory entries
This sets the number of Name cache entries. NSS keeps a cache of the file and directory names it recently looked up. This speeds up opening files and path searches. The default is 2111. The range is 3 to 65521.
nss /NameCacheSize
Set name cache to on or off
This sets Name Cache to ON or OFF. The default is ON.
nss /(No)NameCache
Use percentages instead of integers for cache balancing
This sets the buffers to percentages rather than integers for dynamic balancing of free memory for the buffer cache. The default is ON. Use this switch with /MinBufferCacheSize.
nss /(No)CacheBalance
Set the amount of cache NSS takes from the traditional file system
This is the percent of cache between NSS and the server. The CacheBalance percentage determines how many cache blocks NSS will take from the traditional file system for its own cache. A high cache balance percentage will impede the performance of the traditional file system. A low cache balance will impede the performance of NSS. We recommend that you set the cache balance parameter to equal the percentage of the total disk space you allocate for NSS. However, do not exceed 80 percent. You might want to initially set the parameter at 50 percent and adjust this number as necessary. The default is 60 percent. The range is from 1 to 99 percent.
nss /CacheBalance=value
Limit the number of cache buffers
This is the maximum number of cache buffers you want. Every time you do a cache balance, limit the number of cache buffers to this amount.
nss /cacheBalanceMaxBuffer
Show the cache hit ratio at the server console
This is the number of cache hits divided by the number of attempts to get a file cache buffer from the cache. Any amount above 90 percent is good. This means the system is spending less time going to the disk to retrieve data. Lower numbers indicate NSS needs more memory. If this occurs, you might want to set the cache balance percentage higher.
Cache hit is the number of times that NSS finds the desired file block in the cache buffers.
Cache miss is the number of times that NSS does not find the desired block in the cache buffers.
If you allocate more memory to NSS, the cache hit percentage increases. You can add more memory by adding more physical memory, increasing the cache balance, or increasing the minimum number of cache buffers for NSS. We do not recommend lowering the minimum number of OS cache buffers.
nss /CacheHit
Set the number of Authorization cache entries
This parameter specifies the number of cache buffers that will be used to speed up authorization requests. If many trustees have been set on different files and directories, we recommend that you increase this number. The default is 1024. The range is 16 to 50000.
nss /AuthCacheSize
Determine how often NSS rebalances the amount of cache it uses
This timer lets you determine how often (in seconds) NSS will rebalance the amount of cache it uses according to the total amount of memory on the server. If you have difficulty loading NLMs because of low memory, you might want to lower this timer setting. A lower setting forces NSS to rebalance more often. If your server is stable, you might want to increase this timer so NSS does not work as hard; this will ensure the cache remains balanced. NSS checks the total number of cache buffers to determine if the CacheBalance percentage is met. It then adjusts the timer to provide the appropriate number of cache buffers. The default is 30. The range is 1 to 3600.
nss /CacheBalanceTimer
Set the flush time for modified cache buffers
This sets the flush time for modified cache buffers in seconds. The default is 1 second. The range is 1 to 3600 seconds.
nss /BufferFlushTimer
Show cache buffer statistics
This shows the cache buffer statistics.
nss /CacheStats
Reset cache statistics
This command lets you clear the current statistics and start over. This is useful for checking the results of changes to the system.
nss /reset
Using ConsoleOne to Configure Novell Storage Services
ConsoleOneTM is the primary utility you use to configure and maintain partitions, storage pools, and volumes in NSS. To open ConsoleOne and access the options you need, complete the following:
Open ConsoleOne.
Open the tree you want to work with.
Right-click on the server object you want.
Click Properties.
This opens the ConsoleOne interface where you can access the snap-ins for managing NSS. The NSS configuration features are in the Media snap-in.
Setting Up ConsoleOne on a Workstation
To use ConsoleOne on a client workstation, you need to load ConsoleOne 1.3 or later. Then you must copy the NSS JAR files from your server to your client machine.
Copy these three NSS JAR files to your local LIB directory:
public\mgmt\consoleone\1.3\lib\nssadmin.jar
public\mgmt\consoleone\1.3\lib\nssc1lib.jar
public\mgmt\consoleone\1.3\lib\nssjavalib.jar
Copy these two JAR files to your local RESOURCES directory:
NSS lets you create a RAID 0 device by striping data across multiple drives on your system. This RAID configuration occurs at the software level. You can use this RAID feature for both logical and traditional volumes.
Important information about NSS RAID
Each element in the RAID configuration should come from a different device. NSS will let you obtain RAID elements from the same device, but this will severely impede the performance of your file system.
Currently, the NSS RAID supports RAID 0. This means there is no disk redundancy. If one element in the RAID device malfunctions, the entire configuration is unusable.
NSS RAID can accommodate a maximum of eight segments (amount of space used from each device) on a device per RAID 0 logical device.
The stripe size (amount of data the file system places on one device before moving to the next device) ranges between 4 KB and 256 KB in increments of 2 KB.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Raid Devices > New.
Enter the amount of space you want to obtain from each storage device in megabytes.
Select a segment size.
Select a stripe size.
Select a RAID type.
The RAID type indicates the method of how data is striped across the different disks.
Click Next.
Select the devices you want to use for the RAID configuration.
You can select one or more devices, but select only the ones you want to use for the RAID configuration.
Click Finish.
The file system first creates a virtual device unit, then creates a RAID device.
Deleting a RAID Device
When you delete a RAID device, the file system deletes all the partitions and volumes from all physical storage devices used in the RAID configuration.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Raid Devices.
Select the Raid device you want to delete.
Click Delete.
The file system displays a warning message to ensure you want to delete the RAID device.
Click Yes or No.
Increasing the Size of the RAID Device
You can increase the size of a RAID device by adding more segments from another storage device. You should not place more than one RAID segment on a disk; this will severely impede the performance of your file system.
From ConsoleOne, click Media > Raid Devices.
Select the RAID device you want to increase.
Click Increase Size.
Select the device you want to add to the RAID configuration.
Click Finish.
After you add another physical storage device to your RAID device, you must restripe the configuration. This stripes the data to the other device you added.
NOTE: The file system performance might slow down during the restriping process. Make sure you add all the physical storage devices you want to the RAID device before you click Restripe.
Click Restripe.
The Restripe option recognizes new devices in your RAID configuration and distributes the data across all the devices.
Marking a Device as Sharable for Clustering
Some storage devices exist in a storage area network (SAN). These devices can be shared by multiple servers in a cluster.
IMPORTANT: The system hardware does not specify disk drives to come up automatically as sharable for clustering or not sharable for clustering. You must manually set different devices according to the configuration of your storage system.
The following is important information about making drives Sharable for Clustering:
All portions of an NSS pool must be on a storage device using the Sharable for Clustering feature. This means if you have a storage pool that spans multiple devices, all these devices must be either sharable for clustering or not.
The Sharable for Clustering option is not available for devices that contain the storage pool SYS: or Volume SYS:.
ConsoleOne does not provide the Sharable for Clustering option for devices that contain traditional partitions and volumes.
When you add partitions to a mirror group, all partitions in that group must be either sharable for clustering or not.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Devices.
Select a device.
Select Sharable for Clustering.
Click OK.
Creating a Partition
The first task for setting up NSS is to create partitions on your storage devices for the NSS storage pools and logical volumes.
From ConsoleOne, open the tree you want.
Right-click the server object and select Properties.
Click Media > Partitions > New.
Select a device to create a partition on.
Select the type of partition you want to create (NSS, Traditional, Remote Storage Device).
Enter the size of the partition in bytes (B), kilobytes (KB), megabytes (MB), or gigibytes (GB).
To reserve space for the Hot Fix error correction feature, select Hot Fix and enter the amount of space or percentage you want to reserve.
Mirrored partitions must be compatible in data area size. This means the new partition must be at least the same size or slightly larger than the other partitions in the group. The physical size (combined data and Hot Fix size) of the partition must be at least 100 KB, but no more than 120 MB larger than the data size of the existing partitions in the mirror group.
To mirror the partition, select Mirror and select one of the following options:
Create New Mirror. This option means you are making the partition capable of being part of a mirror group. You do not actually create the group until you add another mirrored partition to the partition you are creating.
Existing Mirror Group. (If you select this option, also select the ID of the mirrored partition.) This shows a list of existing mirror groups that are compatible in data area size. This option lets you add this new partition to one of the mirror groups in the list.
Select a label for the partition (optional).
Click OK.
Deleting a Partition
When you delete a partition you remove all volumes and data on that partition. If the partition is mirrored, the other partitions in the mirror group will retain the data from the deleted partition. If you want to delete a mirrored partition, you must unmirror that partition before you delete it.
Unmirror a partition
From ConsoleOne, open the tree you want.
Right-click the server object and select Properties.
Click Media > Partitions > Mirror.
Select the partition you plan to delete, click Remove.
This removes the partition from the mirror group. You can now delete the partition.
Delete a Partition
From ConsoleOne, open the tree you want.
Right-click the server object and select Properties.
Click Media > Partitions.
Select the partition you want to delete, click Delete.
Creating a Storage Pool
After creating and setting up your partitions, you can create storage pools within the partitions. When you create a storage pool, NSS lets you determine how much space to use from each storage device on your server.
When you create storage pools, you use NSS partitioned or unpartitioned disk space. However, if you choose unpartitioned disk space, a partition and storage pool is created for you at the same time. The storage pool will be the same size as the partition because you can have only one partition per storage pool.
From ConsoleOne, open the tree you want.
Right-click the Server object and then click Properties.
Click Media > NSS Pools > New.
Enter a name for the new storage pool and then click Next.
ZLSS is the default pool (LSS) type.
Select the existing NSS partitions or unpartitioned disk space that you want to use for the pool and then click Next.
If you select an unpartitioned device, you can double-click the number in this column to edit the current amount of space you want to obtain from the storage devices. The storage pool size will be the total of all devices in the pool.
Do one of the following:
If the partition or free space that you selected is not sharable for clustering, the Create Pool dialog box appears with the Activate on Creation check box automatically checked. Click Finish if you want to activate this pool on creation; otherwise, uncheck the box and click Finish.
If the partion or free space that you selected is sharable, the Create Pool dialog box appears with the Activate on Creation and the Cluster Enable on Creation check boxes checked. You must fill in addtional clustering parameters and then click Finish.
For more information on clustering parameters, see Setting Up Novell Cluster Services > Create NSS Pools in the Novell Cluster Services Overview and Installation Guide.
Creating a Logical Volume
After creating storage pools, you can create any number of logical volumes for them according to the physical space available. When you create a logical volume, you can either assign it a space or allow it to expand to the pool size.
The size of a single volume cannot exceed the size of a storage pool. However, the combined sizes of multiple volumes can exceed the size of the storage pool. This is called overbooking. For example, you might have an 800 MB storage pool with eight volumes set at 100 MB each. That is the maximum amount of space you have in the pool. To overbook the pool, you can add volumes or increase the size of existing volumes knowing that not all of the volumes in the storage pool will fill up. If the volumes fill up, you need to add more disk space.
NSS recognizes DOS, Macintosh*, UNIX*, and long name spaces.
From ConsoleOne, open the tree you want.
Right-click the Server object and then click Properties.
Click Media > NSS Logical Volumes > New.
Enter a name for the volume and click Next.
Complete the following steps:
Select the existing storage pool, unpartitioned space, or NSS partitioned space where you want to create your volume and then click Next.
If you select unpartitioned space, NSS creates an NSS partition, then the storage pool, and then the volume.
Enter a quota size for the volume if you want to limit the size of the volume or check "Allow Volume Quota to Grow to the Pool Size" if you want the volume to expand to the size of the pool.
Click Next.
(Conditional) If you chose in Step 5.a to create your volume on NSS partitioned space or free space, enter in the name and size of your NSS pool and then click OK.
Because all volumes must be contained in a storage pool, if you selected free space that did not already contain a volume, NSS will create a pool at the same time that it creates the volume.
Do one of the following:
If the device that you selected is not sharable for clustering, skip to Step 8.
If the device you selected is sharable, determine whether you want to cluster enable the volume on creation. Cluster enabling a volume means that you will assign the volume an IP address so it can be accessed through the Novell client.
If the Cluster Enable on Creation check box is checked, you must fill in addtional clustering parameters. When you have filled in the additional clustering parameters, click Finish and continue with Step 8.
For more information on clustering parameters, see Setting Up Novell Cluster Services > Create NSS Pools in the Novell Cluster Services Administration Guide.
Select the attribute settings you want for the new logical volume from the following list:
Backup. Indicates if the volume should be backed up. Set this flag if the volume contains data you want to back up. Clear this flag if the volume is empty or if backing up the data is unnecessary. This backup option is separate from the third-party backup vendor you use. This means your backup system might not recognize this option whether you select it or not.
Compression. Activates file compression in the logical volumes.
Data Shredding. Activates the Data Shredding security feature. This feature scrambles any data that you delete to prevent anyone from accessing the information with a disk reader. Enter the number of times you want the data shredder to scramble your deleted files. You can select between one and seven times.
Directory Quotas. Activates a feature that lets you assign a maximum quota of space a directory can have
Flush Files Immediately. Activates the feature that flushes all data in a file to disk immediately when you close the file.
Modified File List (MFL). This provides a list of all files modified since the previous backup. A third-party vendor must implement the Modified File List feature in order for you to use it.
Salvage Files. Activates the feature that lets you salvage deleted files. The file system keeps all deleted files in an allocated space until that space is needed for other data. The Salvage feature tracks the files and lets you retrieve the data for a time until the space is needed for other data. You must select this option to salvage the files in the volume.
Snapshot-File Level (File Snapshot). Activates the Snapshot feature at the file level. The Snapshot feature allows the backup utility to capture a snapshot of the last closed version of a file. For example, if your system backs up or crashes while you have a file open, this feature will save a copy of the file before you opened it. You might lose some new information, but you will retain all the previous information.
User Space Restrictions. Activates the user space restrictions feature on the volumes you create.
Activate. Activates logical volumes as soon as you create them.
Mount. Mounts logical volumes as soon as you create them.
Click Finish.
You can now store and manage files in the NSS system.
Renaming a Storage Pool
You can rename existing storage pools. For example, you might want to assign a storage pool name that relates to a department name change.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > NSS Pools.
Select a pool to rename.
Click Rename.
Enter a new name for the pool.
Click Finish.
Renaming a Logical Volume
You can rename logical volumes. For example, you might want to change the name of a volume to reflect the department or organization that uses it.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Logical Volumes.
Click Rename.
Enter a new name for the logical volume.
Click Finish.
Increasing the Size of a Storage Pool
You can increase the size of your storage pools, but you cannot reduce their size.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > NSS Pools.
Select the storage pool you want to increase, then click Increase Size.
Select the storage objects you want to obtain the space from.
Enter the amount of space you want from each storage object in the Used column.
Click Finish.
Deleting NSS Pools or Logical Volumes
You might need to delete a storage pool or a logical volume to create more free space for other storage pools. When you delete a logical volume or a traditional volume from a partition, that partition still owns the space, but you can reassign the space to another storage pool or traditional file system volume. When you delete a partition, ownership of the space in that partition is removed.
After you delete a logical or traditional volume, free space becomes available. You can assign this space to other storage pools to increase their size. You can also use the free space (if you removed NSS ownership) for a traditional file system volume. If necessary, you can restore a volume, see Reviewing and Restoring Deleted Logical Volumes . If you delete a storage pool, you cannot restore any of the volumes in that pool.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > NSS Pools or Logical Volumes.
Select the pool or volume you want and click Delete.
Reviewing and Restoring Deleted Logical Volumes
If you delete a volume, the file system removes it from the storage pool. However, for a specified amount of time, called the Purge Delay time, you can review and even restore the contents of the volume you deleted. For example, you might want to restore information in a volume that was deleted in error. You must retrieve the volume before the delay time elapses; otherwise, the volume is removed from the system and you can no longer access it.
If you delete a storage pool, you delete all the volumes in that pool. You cannot restore volumes.
The default setting for the Purge Delay time is two days. After this time expires, NSS automatically purges the volume.You can change the Purge Delay time to extend or reduce the time for the automatic purging cycle. See Changing the Purge Delay Setting . You can also manually purge deleted volumes. You purge or restore volumes in the "Deleted Logical Volumes on Pool" screen.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Logical Volumes.
Click Deleted Volumes.
Select one of the following options:
Purge. Click Purge to immediately purge all the deleted volumes.
Prevent Purge/Allow Purge. Click Prevent Purge to stop the volume purging process. For example, you might want to access the deleted volume again, or wait until there is less activity on the server. After you click Pause Purge, the button changes to Allow Purge. Click this button to purge the volume.
Salvage. Click Salvage to restore the deleted volume.
Refresh. Click Refresh to rescan the volumes that have been deleted and update the list in the panel.
Click Close when you are finished.
Changing the Purge Delay Setting
The default for the Purge Delay setting is two days. This is the amount of time that you can still access the volume before it is removed from the system. To change the Purge Delay time, enter the following at the server console:
NSS/logicalVolumePurgeDelay=ddd
In this command, you replace ddd with the actual number of seconds to delay the auto purge. The default is 172800 (2 days). For example, if you want to change the Purge Delay time for one day, enter 86400.
The Purge Delay change command is not permanent. You must enter the command each time you restart the server. If you want to make the new setting permanent, enter the command in the AUTOEXEC.NCF file.
Creating a Traditional Volume
NSS is the default file storage and management system in NetWare 6. However, you might want to continue maintaining traditional partitions and volumes in NSS. The following is a list of guidelines for creating traditional volumes in NetWare 6:
NWCONFIG and NSS Menu are not compatible with NetWare 6. Use ConsoleOne to create, mount, modify, and rename traditional volumes.
You can use VREPAIR to fix traditional volumes, but you need to use VERIFY and REBUILD for all logical volumes. For instructions on using VREPAIR, see VREPAIR in the Utilities Reference.
You cannot put traditional volumes in an NSS storage pool.
If you create a traditional volume in NetWare 6, you cannot access that volume from previous releases of NetWare.
You can use ConsoleOne to create, mount, and manage traditional volumes.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Traditional Volumes.
Click New.
Enter a name for the volume and click Next.
Select either partitioned or unpartitioned.
Enter a size for the volume in the Used column and click Next.
Select a block size from the pull-down menu.
Select any of the following options:
Compression. Enables the file system to compress the files in the volume. You set up file compression when you create volumes. Once you enable file compression, you cannot turn it off without creating the volume again.
Migration. Enables the operating system to move infrequently accessed data to remote areas on your server. This creates space for new and more commonly accessed data. Selecting this option only enables the attribute. The data migration feature uses a third-party software package that does the migration function.
Suballocation. Enables the file system to divide partially used disk blocks into suballocation blocks of 512 bytes. These blocks can be used by other data files.
Mount Volume on Creation. Instructs the operating system to mount the volume when you create it. Otherwise, you can mount it later.
Click Finish.
Increasing the Size of a Traditional Volume
To increase the size of a traditional volume, you need to add another segment to that volume.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Traditional Volumes.
Select a volume and click Increase size.
Select the storage device you want to obtain space from.
Double-click on the Used column next to the selected storage device.
Enter the amount of space you want.
Click Finish.
Renaming a Traditional Volume
You can rename a traditional volume.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Traditional Volumes.
Select the volume you want to rename and click Rename.
Enter a name.
Click Finish.
Deleting a Traditional Volume
You can delete traditional volumes.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Traditional Volumes.
Select the volume you want to delete and click Delete.
Dismounting a Traditional Volume
To repair a traditional volume, you need to dismount that volume.
From ConsoleOne, open the tree you want.
Right-click on the server object and select Properties.
Click Media > Traditional Volumes.
Select the volume you want to dismount and click Dismount.
The button label changes to mount.
Repairing a Traditional Volume
Typically, you can't mount a volume if it has even minor damage. Occasionally, a damaged volume mounts and causes errors in the process.
Use VREPAIR to correct volume problems or to remove name space entries from File Allocation Tables (FATs) and Directory Entry Tables (DETs). For instructions on using VREPAIR, see VREPAIR in the Utilities Reference.
You can run VREPAIR on a damaged volume while other volumes are mounted. Following are typical instances when VREPAIR can help:
A hardware failure either prevented a volume from mounting or caused a disk read error.
NOTE: Although VREPAIR can't fix hardware problems, VREPAIR can sometimes fix related volume damage.
A power failure caused a corrupted volume.
The server console displays a mirroring error when the server boots. This mirroring refers to the two copies of FATs and DETs that the operating system keeps (if disks are mirrored, NetWare keeps four copies).
If a volume fails to mount as the server is booting, VREPAIR loads automatically and attempts to repair the volume.
When VREPAIR autoloads, it uses the default options. If you want to use an alternate option, load VREPAIR manually and set the alternate option before running VREPAIR.
NOTE: If you don't want VREPAIR to automatically repair a volume that won't mount, use the SET parameter named Automatically Repair Bad Volumes to change the default.
Prerequisites
The volume you want to repair must be dismounted.
If the volume to be repaired has name space support, the corresponding VREPAIR name space module (V_namespace.NLM) must be located in either the SYS:SYSTEM directory or in a search path directory.
Example modules include V_MAC.NLM and V_LONG.NLM.
Procedure
At the server console prompt, enter
VREPAIR [volume_name] [logfile_name]
(Optional) Replace volume name with the name of the volume to repair. If there is only one volume that is dismounted, you don't need to specify this parameter, since VREPAIR will attempt to repair that volume.
(Optional) If you want to save the error log, replace the logfile_name with the name of the file you want VREPAIR to create. VREPAIR creates a log of errors it finds. VREPAIR displays the errors on screen and will write them to a file if you specify a filename.
When you load VREPAIR, an Options menu is displayed.
Accept the default options, or select alternate options, as appropriate.
The first time you try to repair a volume, accept the default options. If the default options fail to repair the volume, select alternate options.
To accept the default options, continue with Step 3.
To set alternate options at the Options menu, choose Set VRepair Options by typing
2 Enter
To begin the repair process, choose Repair A Volume from the Options menu.
If more than one volume is dismounted, select the volume to repair from those listed.
If only one volume is dismounted, VREPAIR assumes it is the volume that needs repairing and begins the repair.
As the volume is being repaired, the server console screen displays a message indicating VREPAIR activity.
(Optional) Modify error log settings after the repair has started.
If VREPAIR finds many errors during the repair process, you might want to change some of the run-time error settings. To modify these settings after the repair has started, press F1 to display the Current Error Settings menu.
Select Option 1 if you do not want VREPAIR to pause after each error.
Select Option 2 if you want VREPAIR to log errors in a text file.
Select Option 3 to stop the repair of the volume.
Select Option 4 to continue with a volume repair after you have stopped it.
When the repair is complete, answer Y when prompted to write repairs to the disk.
If VREPAIR has found errors, run VREPAIR again by repeating Step 2 through Step 6. Repeat until VREPAIR finds no errors.
If you are unable to mount the volume after running VREPAIR several times, you must delete the volume, re-create the volume using ConsoleOne.
