NAS 1000s Release Notes
Table Of Contents
- Release Notes Information
- Japanese Support for the 1000s
- Services for UNIX® (SFU)
- NFS Performance
- nfsstat -z does not reset the NFS statistical counter
- Cannot assign a client group NFS permissions via the Web UI
- Assign NFS permission to the client group
- Regular users from UNIX/Linux clients cannot change the ownership of a file
- NFS Permissions using the Web UI
- NFS Logging
- NFS administrative shares support
- Volume Mount Points support
- Admin cannot list and map domain users and groups for SFU mapping unless the SFU admin is logged into the domain
- Password Synchronization will not work correctly on a Domain Controller without an Admin UI
- User name mapping Japanese characters
- NFS Performance
- PSM Issues
- Web UI Issues
- NFS Async/Sync Page in the NFS Protocols Properties functions intermittently.
- Enabling telnet via SAK does not start the Telnet Service
- Task Scheduler error when creating a policy and running a WQuinn report from version 5.0
- Unable to select existing quotas for edit and delete
- PSM does not return error message on failed snapshot
- Improper Closure of Terminal Services
- Disabled network cards not visible in Web UI
- Renaming host does not change address bar of browser
- Renaming host forces a restart where the restart page does not refresh
- Altering the Network interface from DHCP to static causes the page not to return
- IP connection metric will not update if Network Port set to DHCP in the Web UI
- Quota Entries do not appear in the Web UI in the Quota Entries page
- Terminal Services returns a VBScript error
- Managing NTFS Mount points
- Default Username and Passwords
- DNS settings configured using the Web UI do not take effect immediately
- Web UI continues to display Orphaned Shares
- Microsoft Powered OS
- Quick Restore Process
- Veritas Backup Exec
- Miscellaneous Issues
NAS 1000s Release Notes 8
5. Select and stop the Server for NFS service.
You will now be able to delete the log using the web interface
as instructed.
6. Start the Server for NFS service.
NFS administrative shares support
SFU does not work with administrative shares in the same fashion
as CIFS. By default, a volume drive such as C: is CIFS shared as
C$. This is an example of an administrative share and is hidden to
CIFS clients. If an NFS share is created and named drive C, as in
the example, the share will not be hidden to NFS clients. This
NFS share will act as a normal NFS share.
Volume Mount Points support
Attempting to create an NFS share on a disk mounted on a mount
point will result in the error:
Cannot write IOCTL to NFS driver…
The HP StorageWorks NAS 1000s supports many
network-sharing protocols, including the NFS protocol for UNIX
and Linux clients. Shares for which the NFS protocol are enabled
must be created on logical disks mounted on a drive letter. A
Windows Powered OS supports mounting virtual disks onto
mount points or reparse points created on another disk already
mounted on a drive letter.
Mount points enable the administrator to mount many disk
devices under a single drive letter, creating the appearance and
behavior of a larger disk drive with a contiguous namespace.
However, the Microsoft Services for UNIX (SFU) NFS Server
does not yet support the functionality of mount points.
All logical disks used for NFS sharing should be mounted on a
drive letter, not on a reparse or mount point. If no NFS shares will
be created on a particular logical disk, that virtual disk may be
mounted on a mount point instead of a drive letter.