Updates were made to the following sections. The changes are explained below.
Section H.7.1, Comparison of NSS on Linux and NCP Volumes on Linux POSIX File Systems
Section H.7.2, Comparison of NSS on NetWare and NSS on Linux
Section H.7.4, Installing and Configuring Novell Storage Services
Section H.7.6, Managing Backup and Restore for Data and Trustee Information
Section H.7.12, Managing Space Quotas for Volumes, Directories, and Users
Section H.7.13, Migrating NSS Devices from NetWare to OES 2 Linux
Section H.7.17, Salvaging and Purging Deleted Volumes, Directories, and Files
Section H.7.18, Securing Access to NSS Volumes, Directories, and Files
Section H.7.20, Using EVMS to Manage Devices with NSS Volumes (Linux)
|
Location |
Change |
|---|---|
|
This entry is new. |
|
|
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. |
|
|
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. |
|
|
NSS management tools on Linux do not support creating nested RAID 0+1 and RAID 5+1. |
|
Location |
Change |
|---|---|
|
Novell AFP for Linux (beginning in OES 2 SP1) Novell CIFS for Linux (beginning in OES 2 SP1) |
|
|
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. |
|
|
NSS management tools on Linux do not support creating nested RAID 0+1 and RAID 5+1. |
|
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. |
|
NSSMU for Linux does not support creating nested RAID 0+1 and 5+1 devices. |
|
Location |
Change |
|---|---|
|
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. |
|
|
This section is new. |
|
Location |
Change |
|---|---|
|
The DFS, CIFS, and AFP features have been separated from the NSS .npm file, and now have .npm files of their own. |
|
Location |
Change |
|---|---|
|
Section 26.2, Using the Event File List to Refine the Backup |
This section is new. |
|
Location |
Change |
|---|---|
|
A folder must be empty before you can delete it. |
|
|
Section 25.7, 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 17.2.1, Differences Between Snapshots on Linux and NetWare |
This section is new. |
|
Location |
Change |
|---|---|
|
Added information about using Novell CIFS for Linux and Novell AFP for Linux when cluster-enabling pools on OES 2 SP1 Linux and later. |
|
Location |
Change |
|---|---|
|
Section 13.5, Creating Software RAID Devices with iManager and |
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. |
|
NSS management tools on Linux do not support creating nested software RAID 0+1 device. |
|
|
NSS management tools on Linux do not support creating nested software RAID 5+1 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. |
|
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. |
|
|
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. |
|
Location |
Change |
|---|---|
|
Added information about how NSS reports space usage to management tools. |
|
|
This section is new. |
|
|
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 |
|---|---|
|
For OES 2 SP1, it is no longer necessary to restart eDirectory after enabling or disabling the Directory Quotas attribute. |
|
|
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. |
|
Location |
Change |
|---|---|
|
This section was modified for clarity. |
|
Location |
Change |
|---|---|
|
The /(no)unplug option is new for OES 2 SP1. |
|
|
Added clarification about the volume ID value in the cluster examples. |
|
|
Added a definition for /ZLSSPoolIOErrors. |
|
|
The /PosixPermissionMask option is new for OES 2 SP1 Linux. |
|
|
Added an example of the output from the volumes command. |
|
Location |
Change |
|---|---|
|
This section was updated for clarity. |
|
|
This section was updated for clarity. |
|
|
This section was updated for clarity. |
|
Location |
Change |
|---|---|
|
This section is new. |
|
|
Section 5.2, Compatibility and Interoperability Issues for NSS |
This section is new. |
|
In OES 2 SP1 and later, the modifier is reported as the user instead of as the root user or nobody user. |
|
|
This section is new. |
|
|
This section is new. |
|
|
This section is new. |
This chapter was revised for clarity.
|
Location |
Change |
|---|---|
|
Moved to the planning section. |
|
|
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. |
|
|
Moved to the planning section. |
|
|
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. |
|
Location |
Change |
|---|---|
|
Section 29.8, NSS Takes Up to 10 Minutes to Load When the Server Is Rebooted |
This section is new. |
|
Section 29.11, Server Hangs When Using an NSS Volume as a Netatalk Share |
This section is new. |
|
Location |
Change |
|---|---|
|
Using Linux POSIX File Systems and NSS Pools and Volumes on the Same Device |
This section is new. |
|
Location |
Change |
|---|---|
|
Updated with support status for using software RAIDs in a Xen-based virtualization environment. |
|
Location |
Change |
|---|---|
|
This section is new. |