Microsoft Services For Unix And Nfs Support - IBM totalstorage 326 User Reference

v If you delete the last persistent image on a volume, and then immediately
v If you use the Windows Powered Disk Defragmenter to attempt to defragment a
Attention:
an inconsistent state. So, if you plan to use the Recovery CD, it is recommended
that you first delete all persistent images to ensure a clean reload of the system
software. For more information on using the Recovery CD, see "Chapter 9. Using
the Recovery and Supplementary CDs" on page 123.

Microsoft Services for UNIX and NFS Support

Support for the Network File System (NFS) is provided in the Model 326 by a
preloaded and preconfigured software component, Microsoft Services for UNIX. The
levels of NFS supported by Services for UNIX, and in turn the Model 326, are NFS
Versions 2 and 3. Any client workstation that supports NFS Version 2 or NFS
Version 3, regardless of the operating system, should be able to connect to the
Model 326 and access its storage as defined by the Model 326 administrator.
To administer NFS file shares and other attributes, use standard Windows
administration tools, including those provided as part of the IBM NAS desktop, and
the Microsoft Windows 2000 for NAS user interface. To support NFS security, you
must perform additional configuration of the User Name Mapping component of
Services for UNIX, which maps the UNIX user name space to the Windows user
name space.
72
Model 326 User's Reference
"insufficient memory available" error message to the system event log. (This
will also cause the failover to fail, which means that either the volume will try
to come online on the "original" node if it is up, or just simply fail to come
online at all.)
– If you increase the size of any cache such that the total cache size of all
volumes on the Model 326 becomes greater than 1 TB, and if you do not
restart the Model 326 after you change the cache size, then no persistent
images can be created on the volume for which the cache size increase was
made. An attempt to create a persistent image on that volume will cause an
error message to be written to the system event log. The event source is
psman5, and the text of the error message is:
There is insufficient memory available.
attempt to create a new persistent image on that volume, the creation of the new
persistent image might fail, and an error message will be written to the system
event log.
The event source is psman5, and the text of the error message is:
A persistent image could not be created due to error 0xc0000043.
This message is generated because when PSM is reinitializing the PSM cache
file on a particular volume (after you delete the last persistent image on that
volume), a new persistent image cannot be created. If this error occurs, wait for a
few minutes, and then try to create the persistent image again.
volume containing persistent images, the volume will not be defragmented. If you
select the volume and click the Defragment button, the Disk Defragmenter will
run on the volume and then indicate that the volume was successfully
defragmented. However, the Analysis display will appear the same as it did
before you clicked Defragment, which indicates that defragmentation did not
take place. You can defragment volumes without persistent images.
The recovery process invalidates persistent images and leaves them in