Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Diagnosing disabled aggregates z/OS Distributed File Service zFS Administration SC23-6887-00 |
|
If zFS detects a problem on an aggregate that is mounted read/write,
zFS attempts to isolate the failure. As a result, zFS might mark an
aggregate unavailable and issue message IOEZ00422E, as shown in the
following example.
In addition, a dump and possibly zFS trace information might be generated. You can contact IBM® service and provide the dump and the trace and any other information that is useful for diagnosing the problem (for example, what was running on the system when the problem occurred). When an aggregate is disabled, applications cannot read from, or
write to, the aggregate. Other aggregates that are not involved in
the failure remain available. However, the disabled aggregate is unavailable
for reading and writing until it is unmounted and mounted. Beginning
with z/OS® V1R13, if the disabled
aggregate is zFS owned on a zFS V1R13 or later system, zFS attempts
to automatically re-enable the disabled aggregate and make it available
again for use.
The preceding re-enablement actions (aggregate movement or internal remount samemode) are taken only if the file system became disabled due to an internal zFS error or a corruption. Note that although the aggregate is disabled, z/OS UNIX System Services continues to display the aggregate mounted as R/W. To determine whether the aggregate has been marked as disabled, use the zfsadm lsaggr command or the zfsadm aggrinfo command. An aggregate that has been disabled might be corrupted, even if it has been disabled and remounted. To be sure that the aggregate is internally consistent, run the ioefsutl salvage batch utility against the aggregate that was disabled, to repair any corruption, and prevent loss of data. See ioefsutl for more information. |
Copyright IBM Corporation 1990, 2014
|