HP CIFS Client A.01.09.02 Release Notes, September 2004

HP CIFS Client A.01.09.02
Features and Fixes in Recent Releases
Chapter 1 5
Features and Fixes in Recent Releases
The following features and fixes are listed, beginning with the most recent release:
For the HP CIFS Client A.01.09.01
Resolve defect of CIFS mount to Windows 2000 server becoming unusable
This fix eliminates a problem where a CIFS mount to a Windows 2000 becomes
inaccessible under certain conditions.
Resolve cifsclientd aborting due to exceeding maximum files per share limit
This fix eliminates an abort caused by files of a mounted share exceeding the previously
supported limit of 8 million files. The new limit is 67 million files per mounted share. A
warning message is logged in the cifsclient log file if limit is exceeded.
Display of CIFS /etc/mnttab entries delayed
A bug has been fixed wherein, on HP-UX 11.0, if the HP CIFS filesystem is mounted using
the “mount -F cifs...” syntax, the results would sometimes not be displayed via the
mount(1M) command for up to several minutes. This fix ensures that no delay occurs.
NOTE This fix applies only to HP-UX 11.0.
Misleading error if lookup of server address fails
When a user attempts to cifslogin to a mounted CIFS server, if the server’s IP address
cannot be found (gethostbyname(3N) fails), the CIFS Client displays the system error
message is “No such device or address”. The message is chosen from the standard Unix
system errors. Previously, the error was the somewhat misleading “Host is down”.
”\” delimiters lost in cifsclient status mntck function
This fix addresses an obscure problem. When the status option is specified with the
cifsclient control script (/opt/cifsclient/bin/cifsclient), a new mntck function, which
checks for stale CIFS mounts, is called. If there is a stale mount, and the CIFS Client is
down, and the configuration parameter mtabName is not null, then the “\” characters that
delimit the server and share names of the stale mount would be lost in the output of the
mntck function. This fix corrects that problem.