Re: repairing a corrupted HFS file / *IGW024E HFS DATA SET: xxx
You're dead, as far as I know. IBM never designed an fsck for either of their z/OS UNIX filesystems. I was under the impression that the MOUNT itself had the fsck fixing in it. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Dr. Stephen Fedtke Sent: Tuesday, August 30, 2011 12:21 PM To: IBM-MAIN@bama.ua.edu Subject: repairing a corrupted HFS file / *IGW024E HFS DATA SET: xxx hi all, we get the following error: *22.07.42 *IGW024E HFS DATA SET: SHERLOCK.SHRLCK.HFS * INTERRUPTED DURING FILE SYSTEM SYNC. PROBABLE HFS CORRUPTION. * READ-WRITE MOUNT REJECTED the literature does not tell anything about a quick option to repair or re-sync a corrupted hfs file. is there really no way to easily repair the hfs? best, many thanks! stephen p.s.: in meantime, a big thank for all answers on other questions we posed. --- Dr. Stephen Fedtke Enterprise-IT-Security.com Seestrasse 3a CH-6300 Zug Switzerland Tel. ++41-(0)41-710-4005 www.enterprise-it-security.com ++NEWS++ SF-NoEvasion lets you avoid all 10 pitfalls when connecting z/OS to your SIEM ++NEWS++ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: repairing a corrupted HFS file / *IGW024E HFS DATA SET: xxx
I've never successfully repaired a damaged HFS. The best you can do is either restore from a backup copy or define a new file system and using the copytree command copy as much as the damaged file system to the new file system as possible. Then mount the new file system at the original mount point. You should consider migrating to zFS from HFS's since they're much more resilient to errors of this type. Mark Jacobs On 08/30/11 13:21, Dr. Stephen Fedtke wrote: hi all, we get the following error: *22.07.42 *IGW024E HFS DATA SET: SHERLOCK.SHRLCK.HFS * INTERRUPTED DURING FILE SYSTEM SYNC. PROBABLE HFS CORRUPTION. * READ-WRITE MOUNT REJECTED the literature does not tell anything about a quick option to repair or re-sync a corrupted hfs file. is there really no way to easily repair the hfs? best, many thanks! stephen p.s.: in meantime, a big thank for all answers on other questions we posed. --- Dr. Stephen Fedtke Enterprise-IT-Security.com Seestrasse 3a CH-6300 Zug Switzerland Tel. ++41-(0)41-710-4005 www.enterprise-it-security.com ++NEWS++ SF-NoEvasion lets you avoid all 10 pitfalls when connecting z/OS to your SIEM ++NEWS++ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Mark Jacobs Time Customer Service Tampa, FL Some people are electrifying, they light up a room when they leave. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: repairing a corrupted HFS file / *IGW024E HFS DATA SET: xxx
On Wed, Aug 31st, 2011 at 3:26 AM, McKown, John wrote: You're dead, as far as I know. IBM never designed an fsck for either of their z/OS UNIX filesystems. I was under the impression that the MOUNT itself had the fsck fixing in it. And fsck is typically more concerned with ensuring a valid (consistent ?) filesystem exists, not necessarily that all the files contained within survive intact. There are exceptions - the designers of (Suns) ZFS were so enamoured with their handiwork they took years to accept that they even needed a fsck. Mighty impressive piece of work, but it still broke. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
