IT17195: COPYING A FILE TO AN NFS STATIC MOUNT VIA THE CLI INCORRECTLY REPORTS SUCCES WHEN THE MOUNT IS DOWN
Fixes are available
Fix packs for DataPower Service Gateway version 7.0
Fix packs for DataPower B2B Appliance version 7.0
Fix packs for DataPower Integration Appliance version 7.0
Fix packs for DataPower Gateway version 7.1
Fix packs for DataPower Gateway version 7.2
Fix packs for DataPower Gateway version 7.5
Fix packs for DataPower Gateway version 7.5.1
Fix packs for DataPower Gateway version 7.5.2
Closed as program error.
When configuring an NFS Static Mount to enable Local-filesystem-access, DataPower allows the user to access the NFS directory via the nfs-MountName directory. From the CLI you can copy files to and from the NFS static mount in the following manner: # copy local:///somefile.txt nfs-MountName:///somefile.txt When the NFS mount is not up, the nfs-MountName directory is still accessible, thus a user can still copy files to this location; however, these files are not successfully transferred to the remote NFS server. In this case, the copy command will succeed and provide the following success message: File copy success (X bytes copied) However, checking the NFS remote server will yield that no file has been copied.
Affected is the use of local file system access with an NFS mount. Copying to the mount directory is still allowed even if the NFS mount attempt was not successful. This causes a message indicating success to be issued even though the file did not actually make it to the NFS server.
Fix is available in 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124 and 126.96.36.199 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels