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
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
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
@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
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
, 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
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
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
8 matches
Mail list logo
