Troubleshooting
Problem
Mount of a zFS file system fails with return code = 0000008D reason code = EF096271 because the aggregate is being attached read-only and the necessary log recovery cannot be run. See Appendix A in the DFS/SMB/zFS Messages and Codes manual for the description of the zFS reason code.
Symptom
BPXF029E ROOT FILE SYSTEM OMVS.ERPD10.ROOT.ZFS
WAS NOT MOUNTED. RETURN CODE = 0000008D, REASON CODE = EF096271
Cause
If a zFS file system is mounted read-write (in order to apply maintenance, for example) and the file system is not unmounted cleanly, zFS will need to run log recovery on the next mount. If the next mount is a read-only mount, zFS will not be able to run recovery and the mount will fail.
Resolving The Problem
Mount the file system as read-write so that recovery can be run, then remount as read-only.
To avoid this mount failure in the future, you can specify the romount_recovery=on configuration option to allow zFS to temporarily mount the aggregate read-write, replay the log, and then mount the aggregate read-only. You can turn on this read-only mount recovery behavior using the IOEFSPRM configuration option romount_recovery=on. Alternatively, you can issue the 'zfsadm config romount_recovery on' command. This option was added in z/OS 1.7 and z/OS 1.8 via APAR OA22351 and z/OS 1.9 via APAR OA20615, and is available on z/OS 1.10 and higher.
Related Information
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3T1012568