Novell Doc: NW 6.5 SP8: NSS File System Administration Guide

J.2.1 Comparison of NSS on Linux and NCP Volumes on Linux POSIX File Systems

Location	Change
File access protocols	This entry is new.
User space quotas (user space restrictions)	For NCP volumes on Linux: Yes, if the Linux file system being used under the NCP share supports user quotas and the Linux file system resides on a local, iSCSI, or Fibre Channel drive. All users of the NCP volume must be LUM enabled. Manage the user quotas using the Linux file system tools.
Volume name space	For NSS on OES 2 SP1 Linux, the default name space used when mounting NSS volumes is changed from UNIX to Long. This improves performance over using UNIX.
Software RAID support	NSS management tools on Linux do not support creating nested RAID 10 and RAID 15.

J.2.2 Comparison of NSS on NetWare and NSS on Linux

Location	Change
File access protocols	Novell AFP for Linux (beginning in OES 2 SP1) Novell CIFS for Linux (beginning in OES 2 SP1)
Volume name space	For NSS on OES 2 SP1 Linux, the default name space used when mounting NSS volumes is changed from UNIX to Long. This improves performance as compared to using UNIX.
Software RAID support	NSS management tools on Linux do not support creating nested RAID 10 and RAID 15.

Location

Change

File access protocols

Novell AFP for Linux (beginning in OES 2 SP1)

Novell CIFS for Linux (beginning in OES 2 SP1)

Volume name space

For NSS on OES 2 SP1 Linux, the default name space used when mounting NSS volumes is changed from UNIX to Long. This improves performance as compared to using UNIX.

Software RAID support

NSS management tools on Linux do not support creating nested RAID 10 and RAID 15.

J.2.3 Cross-Platform Issues for NSS

Location	Change
Section 7.5.1, Storage-Related Plug-Ins for Novell iManager 2.7	The support matrix was updated to include Novell CIFS for Linux and Novell AFP for Linux in OES 2 SP1.
Section 7.5.5, Management Capabilities for Software RAIDs	NSSMU for Linux does not support creating nested RAID 10 and 15 devices.

J.2.4 Installing and Configuring Novell Storage Services

Location	Change
EVMS Requirements	IMPORTANT:If you move devices that contain NSS pools cross-platform (such as reassigning SAN-based devices from a NetWare server to an OES 2 Linux server), NSS recognizes the pools and automatically uses EVMS to manage the devices.
Section 3.6, Updating NSS on OES 2 Linux	This section is new.

J.2.5 Management Tools for NSS

Location	Change
Section 9.1.1, Understanding Storage-Related Plug-Ins	The DFS, CIFS, and AFP features have been separated from the NSS .npm file, and now have .npm files of their own.

J.2.6 Managing Backup and Restore for Data and Trustee Information

Location	Change
Section 29.2, Using the Event File List to Refine the Backup	This section is new.
Section 29.5.2, NetWare	This section is new.

J.2.7 Managing Files and Folders on NSS Volumes

Location	Change
Section 28.2.1, Prerequisites	A folder must be empty before you can delete it.
Section 28.5, Viewing or Modifying File or Folder Properties	The Copy Inhibit attribute works only for clients using Macintosh operating systems to access NSS volumes on NetWare. If the directory quota exceeds the volume quota, the volume quota is enforced.

Location

Change

Section 28.2.1, Prerequisites

A folder must be empty before you can delete it.

Section 28.5, Viewing or Modifying File or Folder Properties

The Copy Inhibit attribute works only for clients using Macintosh operating systems to access NSS volumes on NetWare.

If the directory quota exceeds the volume quota, the volume quota is enforced.

J.2.8 Managing NSS Pool Snapshots

Location	Change
Section 18.2.1, Differences Between Snapshots on Linux and NetWare	This section is new.
Section 18.2.9, Guidelines for Viewing a List of Snapshots that are Stored in a Pool (NetWare)	This section is new.

J.2.9 Managing NSS Pools

Location	Change
Section 16.2, Creating a Pool	Added information about using Novell CIFS for Linux and Novell AFP for Linux when cluster-enabling pools on OES 2 SP1 Linux and later.

J.2.10 Managing NSS Software RAID Devices

Location	Change
Section 13.5, Creating Software RAID Devices with iManager and Section 13.6, Creating Software RAID Devices with NSSMU	IMPORTANT:Unallocated partitions (that is, partitions that are not mirrored and do not contain pools or other file systems), are deleted in order to present the unused space as free space for use by the RAID. No data loss occurs by this action.
Section 13.9, Creating a Software RAID 10 with NSSMU (NetWare)	NSS management tools on Linux do not support creating nested software RAID 10 device.
Section 13.10, Creating a Software RAID 15 with NSSMU (NetWare)	NSS management tools on Linux do not support creating nested software RAID 15 device.
Section 13.12, Increasing the Size of a Software RAID Device	IMPORTANT:If the software RAID device is shared in a cluster, connect to the node where the RAID is currently active to manage the RAID and increase the size of the RAID. A device must be the same size or larger than the segment size being used in the RAID. You might need to add or initialize a new device, then try again. While restriping, the new device is considered a failed device until it is completely resynchronized. While expanding a RAID 5 device, if one of the drives goes down (either one of the existing segments or the newly added segment), the pool deactivates. If you remove any device from a RAID 5 other than the one that was just added for restripe, it considers that as a two-disk error, and deactivates the RAID and the pool.
Section 13.13, Restriping a Software RAID 0 or 5 Device	When expanding a RAID 5 on Linux, if the newly added drive goes down during the restripe, the restriping continues without the new partition and puts the RAID in a degraded state with one partition missing. If the same partition comes back online, it finishes the restripe. If the partition has completely failed, after the degraded restriping is complete, you can add a new replacement partition, and the RAID restripes to fix it. When expanding a RAID 5 on NetWare, if the newly added drive fails during the restripe, this is considered a fault and the device and its pools are automatically deactivated. If the same partition comes back online, it finishes the restripe. If the partition is failed, this is not handled. You must recover from backup. (Handling this type of failure with a degraded restripe recovery (same as for RAID 5 on Linux) is planned for a future release.)
Section 13.14, Replacing a Failed Segment in a Software RAID	IMPORTANT:If a second segment fails before the restriping is completed for the first drive replacement, this is considered a two-drive failure. You must recover data from a backup copy.

J.2.11 Managing NSS Volumes

Location	Change
Section 19.2.1, Guidelines for Sizing Volumes	Added information about how NSS reports space usage to management tools.
Section 19.2.3, Guidelines for NSS Volumes in a Cluster	This section is new.
Lookup Namespace	For OES 2 SP1 Linux and later, Long is the default name space instead of UNIX. For Linux, NCP tools can be used only when Long or UNIX is set as the primary name space. The UNIX name space supports some special characters that are not allowed in the Long name space, such as characters 0x01 through 0x07 and 0x10 through 0x1f. If you need to use these special characters in filenames, choose UNIX as the primary name space.

Location

Change

Section 19.2.1, Guidelines for Sizing Volumes

Added information about how NSS reports space usage to management tools.

Section 19.2.3, Guidelines for NSS Volumes in a Cluster

This section is new.

Lookup Namespace

For OES 2 SP1 Linux and later, Long is the default name space instead of UNIX.

For Linux, NCP tools can be used only when Long or UNIX is set as the primary name space.

The UNIX name space supports some special characters that are not allowed in the Long name space, such as characters 0x01 through 0x07 and 0x10 through 0x1f. If you need to use these special characters in filenames, choose UNIX as the primary name space.

J.2.12 Managing Space Quotas for Volumes, Directories, and Users

Location	Change
Section 25.1, Understanding Space Quotas	For OES 2 SP1, it is no longer necessary to restart eDirectory after enabling or disabling the Directory Quotas attribute.
Section 25.4.6, Configuring User Space Quotas on Volumes After Upgrading or Migrating from OES 1 Linux (Linux)	You cannot use the Linux chown command to change the creator field for the NSS file system. It changes the root user’s view of who is reported as the owner user in the Linux path, but the change has no effect on the NSS metadata.

J.2.13 Migrating NSS Devices from NetWare to OES 2 Linux

Location	Change
Section 11.1.1, Media Format	This section was modified for clarity.

J.2.14 NSS Commands

Location	Change
Section A.5.5, UnplugAlways Command for the Read Queue	The /(no)unplug option is new for OES 2 SP1.
Section A.25, noatime and atime Commands	/atime and /noatime options are new for NetWare 6.5 SP8 (same as OES 2 SP1 NetWare). Added clarification about the volume ID value in the cluster examples.
Section A.27, Opportunistic Locking (Oplock) Commands	Added a definition of opportunistic locking.
Section A.29.1, Pool Status	Added a definition for /ZLSSPoolIOErrors.
Section A.32, POSIX Permission Mask Command (Linux)	The /PosixPermissionMask option is new for OES 2 SP1 Linux.
Section A.40, Transaction Tracking System (TTS) Commands (NetWare)	To disable TTS for volume VOL1, enter the following at the server console: nss /noTransaction=VOL1
Section A.42.2, Volumes Command	Added an example of the output from the volumes command.

J.2.15 NSS Utilities

Location	Change
Section B.16, RAVSUI (Linux)	This section was updated for clarity.
Section B.17, RAVVIEW (Linux)	This section was updated for clarity.
Section B.24, VOLUMES (Linux, NCP Utility)	This section was updated for clarity.

J.2.16 Planning for NSS Storage Solutions

Location	Change
Section 5.1.7, Storage Features	This section is new.
Section 5.2, Compatibility and Interoperability Issues for NSS	This section is new.
Section 5.4.5, UTF-8 Naming Considerations in Mixed-Language Environments (NetWare)	This section is new.
Linux-Enabled eDirectory Users	In OES 2 SP1 and later, the modifier is reported as the user instead of as the root user or nobody user.
File Access for Users	This section is new.
Section 5.7, Antivirus Support for NSS	This section is new.
Section 5.9, NSS Support for Memory Mapped Files	This section is new.

J.2.17 Salvaging and Purging Deleted Volumes, Directories, and Files

This chapter was revised for clarity.

J.2.18 Securing Access to NSS Volumes, Directories, and Files

Location	Change
eDirectory Users	Moved to the planning section.
Linux-Enabled eDirectory Users	Users who access NSS via Samba, NFS, or third-party AFP protocols must be Linux-enabled in order for user quotas to work for them. Moved to the planning section.
Section 5.5.5, How NSS Uses Novell Linux User Management	Moved to the planning section.
Section 5.6, File Access for Users	In OES 2 SP1 Linux and later, users can also access NSS volumes using Novell CIFS, Novell AFP, and Domain Services for Windows. Moved to the planning section.

J.2.19 Troubleshooting the NSS File System

Location	Change
Section 33.9, NSS Takes Up to 10 Minutes to Load When the Server Is Rebooted (Linux)	This section is new.
Section 33.13, Server Hangs When Using an NSS Volume as a Netatalk Share	This section is new.

J.2.20 Tuning NSS Performance on NetWare

Location	Change
Section 30.8, Tuning NSS Write Performance on NetWare	This section is new.

J.2.21 Using EVMS to Manage Devices with NSS Volumes (Linux)

Location	Change
Using Linux POSIX File Systems and NSS Pools and Volumes on the Same Device	This section is new.

J.2.22 Using NSS in a Virtualization Environment

Location	Change
Using RAIDs	Updated with support status for using software RAIDs in a Xen-based virtualization environment.

J.2.23 What’s New

Location	Change
Section 2.1, What’s New for NSS (NetWare 6.5 SP8)	This section is new.

J.2 December 2008 (NetWare 6.5 SP8)

J.2.1 Comparison of NSS on Linux and NCP Volumes on Linux POSIX File Systems

J.2.2 Comparison of NSS on NetWare and NSS on Linux

J.2.3 Cross-Platform Issues for NSS

J.2.4 Installing and Configuring Novell Storage Services

J.2.5 Management Tools for NSS

J.2.6 Managing Backup and Restore for Data and Trustee Information

J.2.7 Managing Files and Folders on NSS Volumes

J.2.8 Managing NSS Pool Snapshots

J.2.9 Managing NSS Pools

J.2.10 Managing NSS Software RAID Devices

J.2.11 Managing NSS Volumes

J.2.12 Managing Space Quotas for Volumes, Directories, and Users

J.2.13 Migrating NSS Devices from NetWare to OES 2 Linux

J.2.14 NSS Commands

J.2.15 NSS Utilities

J.2.16 Planning for NSS Storage Solutions

J.2.17 Salvaging and Purging Deleted Volumes, Directories, and Files

J.2.18 Securing Access to NSS Volumes, Directories, and Files

J.2.19 Troubleshooting the NSS File System

J.2.20 Tuning NSS Performance on NetWare

J.2.21 Using EVMS to Manage Devices with NSS Volumes (Linux)

J.2.22 Using NSS in a Virtualization Environment

J.2.23 What’s New