HP ProLiant Storage Server Release Notes (January 2006)

Storage Server release notes 31
Issue: Administrator/root username mapping not working
Description An issue occurs when the Windows local administrator is mapped to the UNIX
root user, and the local administrators group is mapped to the UNIX group id of
the root user (for example, sys). When a file is created by the Windows local
administrator on an NFS share, the file will have owner nobody and group
nogroup (4292967294 on Linux) when viewed from the NFS client. This issue
applies to the following storage servers using Service for Unix version 3.5 (SFU
3.5): HP Proliant Storage Server DL100, ML110, ML110 G2, ML350 G4,
ML370 G4/G4p, DL380 G4, DL585, and HP StorageWorks NAS 500s.
Workaround HP engineers are working to resolve this issue. In the meantime, use the chown
command on the NFS client to set the owner and group.
Issue: Large I/O on an NFS mount point hangs NFS server
Description Large I/O on an NFS mount point hangs NFS server.
Workaround If you experience a problem with the NFS server not responding, increase the
read/write buffer size.
Increase the buffer size by changing the mount options to:
mount -o rsize=32768,wsize=32768 server:/share /mount
If the NFS client is in a hung state, the client may need to be rebooted and the
NFS server service may need to be restarted on the storage server. To restart the
NFS server service on the storage server, do the following:
1. Open a command prompt.
2. Type net stop nfssvc.
3. Type net start nfssvc.
Issue: CIFS client and Explorer on the server are not able to open NFS client created files
Description After you delete files from a location that is shared by Server for NFS, the files do
not immediately go away. Although the files seem to remain, you cannot use the
files. This problem can also cause a message that states that the file is in use
when you try to save the file from a program on the server or from an SMB client
computer. Both symptoms last for approximately 30 seconds.
Workaround After 30 seconds, the file will disappear from the Explorer window, and you can
save new versions of the file.
Issue: File sizes are not reflecting properly on server
Description If you mount a Windows share from an NFS client and copy files onto the same
NFS share, the accurate size of the files may not be immediately displayed on
the storage server.
Workaround The storage server may take a few minutes to reflect the correct file size.
Issue: Clearing the NFS log via the WebUI causes the log file to become inaccessible
Description When clearing the NFS logs via the WebUI, the log file clears, but the file
permissions are set incorrectly. Access to the log c:\SFU\logs with Windows
Explorer is denied.
Workaround Stop the Server for NFS service, clear the NFS log, and then start the Server for
NFS service. The log file is then accessible.