Re: zfs fails to start
Just found this information related to the ZFS delay I'd had, which I'd filed away. It's copied from a redpiece. I chopped bits out here and there I think, but the full text is in the following Redpiece: http://www.redbooks.ibm.com/redpieces/pdfs/sg246580.pdf 2.12.2 Mounting zFS file systems copied outside the sysplex If you have a specific system located in another sysplex that is used for preparing and servicing UNIX System Services file systems that are type zFS, then the first mount may take at least 65 seconds. This is caused by the write protection implementation. As long as the aggregate is attached read-write, the identifier is active in block zero (0). As a result, on ADRDSSU COPY or DUMP processing, it is copied as well. When you mount or attach the aggregate in the target production system, zFS sees this identifier. Because it does not reflect the sysplex environment, zFS waits 65 seconds for an update of the time stamp value within the identifier. If the aggregate is used read-write outside of the sysplex, then this time stamp should get updated twice a minute, as mentioned earlier. If no update occurs, this shows that the identifier is there without a reason. In this case, after the 65 seconds, zFS attaches and mounts the aggregate. To avoid the 65 seconds wait time on access to the aggregate in the production environment, unmount or detach the source aggregate in the service system before using ADRDSSU COPY or ADRDSSU DUMP. OR Switch the source aggregate to read-only access, using the ISHELL modify interface from the mount table panel or the /usr/sbin/chmount shell command. Then copy the contents of the aggregate. This switch removes the write protection identifier, as well. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
zfs fails to start
Has anyone ever had the problem of zfs not starting? No messages in the log; can't issue any queries, etc. because OMVS is not up - it's waiting on ZFS! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: zfs fails to start
I've had problems at IPL due to the RESOLVER address space not starting. I don't remember the ZFS started task failing. On my system, I can still bring up NET and TSO, so I can look in the z/OS SYSLOG. If you have an MAS, can you look at the failing system's SYSLOG? -- 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 Betsy Jeffery Sent: Monday, April 16, 2012 10:06 AM To: IBM-MAIN@bama.ua.edu Subject: zfs fails to start Has anyone ever had the problem of zfs not starting? No messages in the log; can't issue any queries, etc. because OMVS is not up - it's waiting on ZFS! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: zfs fails to start
You might want to put a jobcard in SYS1.STCJOBS so that you can look at the JOBLOG. You just create a member called ZFS. //ZFSJOB (acctcode),TIME=NOLIMIT,MSGCLASS=H /*ROUTE PRINT LOCAL //ZFS EXEC ZFS -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Betsy Jeffery Sent: Monday, April 16, 2012 11:06 AM To: IBM-MAIN@bama.ua.edu Subject: zfs fails to start Has anyone ever had the problem of zfs not starting? No messages in the log; can't issue any queries, etc. because OMVS is not up - it's waiting on ZFS! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: zfs fails to start
Syslog has no zfs releated messages at all! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: zfs fails to start
Only a guess, but If you didn't shutdown cleanly, OMVS can take a long time to come up while it cleans up each filesystem. How long did you wait to decide there was a problem? Otherwise, did something get messed up in IEASYSxx? _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Betsy Jeffery Sent: Monday, April 16, 2012 11:06 AM To: IBM-MAIN@bama.ua.edu Subject: zfs fails to start Has anyone ever had the problem of zfs not starting? No messages in the log; can't issue any queries, etc. because OMVS is not up - it's waiting on ZFS! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: zfs fails to start
Thanks all. I found (I think) the culprit. The BPXPRMxx SYSPLEX parm had been changed to 'YES'. I reset it to 'NO' (we are a monoplex) and ZFS initialized. My guess (and I emphasize guess) would be that since some of the zfs files are copied from another LPAR they would have the other LPAR's system id. Sysplex yes might have caused it to wait/look for the other system. Each LPAR image is standalone. Regards, Betsy -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: zfs fails to start
Yeah, that could have been it. I believe it waits something like 1 minute, and then continues. If your ZFS shutdown wasn't clean, it may have also been checking each ZFS filesystem, which can take a lot of time if you have a lot of ZFS filesystems. You'd see messages on the SYSLOG for this though. I've had issues in the past (not quite had time to find out why) with Resolver starting up too soon - I have to cancel it, which then causes OMVS to spring into life and finish initialising. D OMVS,A=ALL can be useful to see what is going on. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
