Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
BPXF027I z/OS MVS System Messages, Vol 3 (ASB-BPX) SA38-0670-00 |
|
BPXF027I FILE SYSTEM name MOUNT DELAYED BECAUSE
MOUNT POINT mpname CANNOT BE RESOLVED. RETURN CODE
= retcode, REASON CODE = reason ExplanationOMVS was unable to resolve the mount point path name while attempting to mount a file system that was mounted by another system in the sysplex. The file system that contains the mount point may have become inaccessible because the system that was serving the file system failed and sysplex partition recovery processing could not establish a new file system server. No mounts that have mount points in the inaccessible file system will succeed until the inaccessible file system is recovered. For example, if the file system is mounted with the Automove=NO option then no attempt is made to recover the file system. Another example is that mount point directory may have been removed if the mount point file system was owned by another system that had not yet processed the mount. In this case, the file system should be unmounted from the owning system, since it will not be accessible. In the message
text:
System actionThe mount will be reattempted the next time a mount is processed in the sysplex. At that time, another attempt will be made to resolve the mount point path name and complete the mount.However, if the mount point directory has been removed, the mount will never be successful. Operator responseContact the system programmer. System programmer responseIf a file system containing one of the directories in the mount point path name is not mounted, then mount it. If one of those directories has been renamed, then restore the original name, either by again renaming the directory or by creating a symbolic link with the old name. If the mount point directory has been removed, then unmount the file system from the owning system and mount it again on a valid mount point. ModuleBPXTXRMT Sourcez/OS UNIX System Services kernel (BPX) Routing Code2 Descriptor Code4 |
Copyright IBM Corporation 1990, 2014
|