OA67083: BIND MOUNT FAILURE RC79 EINVAL RSN055B005A BPXFSMNT JRFSNOTSTART BPXTXPFS BPXF274I

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When attempting to bind mount a filesystem, a mount failure
  occurs with RC79 EINVAL RSN055B005A JRFSNotStart. This failure
  may surface as a BPXF274I message:
  
  BPXF274I FILE SYSTEM OMVS.ZFS.MYFS 797
  FAILED TO MOUNT.
  RETURN CODE = 00000079, REASON CODE = 055B005A
  
  You can also see the failure in D OMVS,MF output showing a
  TYPE=BPXTXPFS:
  
  D OMVS,MF
  BPXO058I 12.01.21 DISPLAY OMVS 841
  OMVS     0010 ACTIVE             OMVS=(xx)
  SHORT LIST OF FAILURES:
  TIME=10.54.31  DATE=2024/10/03        MOUNT RC=0079
  RSN=055B005A NAME=OMVS.ZFS.MYFS
  TYPE=BPXTXPFS
  PATH=59999946ae95bf06c92bb074d0babd0abe34058fb/merged/etc/hosts
  
  If attempting to mount from the shell, the failure may also be
  shown in a FOMF0504I message:
  
  # /usr/sbin/mount --bind src /mnt
  FOMF0504I mount error: 79 55B005A
  EINVAL: The parameter is incorrect
  JRFSNotStart: The file system specified was not started
  
  ANALYSIS: The mount failure occurs when a bind mount is issued
  and the source path resides on a function-shipping client.
  
  
  VERIFICATION STEPS:
  1. Determine which filesystem the source (src) from the bind
  mount resides on.  If you are able to determine which part of
  the path is the mountpoint, you
  can use this mountpoint path as input to a 'df' shell command.
  2. In the 'df' output, CLIENT=Y will be specified.
  
  ADDITIONAL KEYWORDS: MSGBPXF274I MSGFOMF0504I
  
  
  FIXCAT KEYWORD:
  ZOSCP/K
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of z/OS UNIX System Services for                   *
  * HBB77D0 HBB77E0 using bind mount                             *
  * in the shared filesystem configuration                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In the shared filesystem environment,                        *
  * a bind mount attempt may fail with                           *
  * RC79 EINVAL RSN055B005A JRFSNotStart.                        *
  * It happens when the bind mount is                            *
  * issued on the system where the bind                          *
  * mount source path resides on                                 *
  * a function-shipping file system.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Bind mount processing obtains file system type of the source
  from VfsGfs. If the source file system is function-shipped,
  the VfsGfs points to XPFS that is an internal PFS. So the
  bind mount fails.
  

Problem conclusion

• Changed the logic in module BPXVRCHM so that bind mount
  processing will obtain the file system type from VfsNativeGfs.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UJ96585 UJ96782

Modules/Macros

• BPXFSMNT BPXFSLIT BPXVRCHM
  

Fix information

• Fixed component name

  OPENMVS SYS SRV

• Fixed component ID

  5695SCPX1

Applicable component levels

• R7D0 PSY UJ96782

     UP25/03/26 P F503

• R7E0 PSY UJ96585

     UP25/03/26 P F503

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.