Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only

  • 1.  Corrupted HFS filesystem

    Posted Mon July 11, 2011 02:11 AM
    Hello !
    I (and also a colleague of mine) have run into the same problem and got the following message when IPL:ing:
    IGW024E HFS DATA SET: JVA600.HFS
    Interrupted during file system data sync. Probable HFS corruption.
    read-write mount rejected.

    This was probably due so a not clean shutdown of zOS.
    Is there a simple/better way of recovering from this other than reactivating the original zOS volumes ?

    Bo Nilsson
    bonils


  • 2.  Re: Corrupted HFS filesystem

    Posted Mon July 11, 2011 07:18 AM
    Bo,
    You actually have a couple or choices. If you had a backup of the file system you could restore just the HFS from there. Since you probably do not have a backup, you will need to restore the entire volume where JVA600.HFS resides. I believe JVA600.HFS is on SBPRD3.

    RDzJohn
    RDzJohn


  • 3.  Re: Corrupted HFS filesystem

    Posted Wed July 13, 2011 07:45 AM
    Bo,
    I experienced the same situation. There is another way to get rid of it:
    • define a new HFS (JVA600.HFS.NEW, for example)
    • mount the new file in some new directory
    • copy everything you have in your old mount point for JVA600.HFS to the new directory
    • unmount both HFS
    • rename JVA600.HFS to JVA600.HFS.OLD and JVA600.HFS.NEW to JVA600.HFS
    • mount it again.

    You find a similar procedure in the chapter "Create new HFS files for /tmp and /u" in the redbook SC14-7281-01 "RDz UT Configuration Guide". They also have scripts to copy the full tree.

    Take care that you should only do that if you are sure that you have a "false positive", i.e., your file system is OK, z/OS only thinks it could be corrupted!

    Regards,

    Rodney
    Krick


  • 4.  Re: Corrupted HFS filesystem

    Posted Wed July 13, 2011 01:18 PM
    This is a very dangerous proposition and not one we would recommend. If you have a corrupted HFS you must assume the contents of the HFS and the corresponding metadata has been corrupted. Copying from a corrupted HFS may result in a corrupted copied HFS.

    RDzJohn
    RDzJohn


  • 5.  Re: Corrupted HFS filesystem

    Posted Sat July 16, 2011 02:32 AM
    John,

    I agree with you, of course! This is why I've written:
    "Take care that you should only do that if you are sure that you have a "false positive", i.e., your file system is OK, z/OS only thinks it could be corrupted!"
    In the case of JVA600, this is the Java Runtime and it is normally READ ONLY. In this case I don't see any problems in doing that.

    Rodney Krick
    http://www.aformatik.com
    Krick


Related Content