You should mount the "sysres" zFS files read only (as you should have been doing with HFS also). But also make sure you have this in your zFS parms:
romount_recovery=on /* see APAR OA22351 */ Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Sat, 22 May 2010 23:19:28 +1000, Shane Ginnane <ibm-m...@tpg.com.au> wrote: >Radoslaw, this sounds like journal (log) replay issues. >I guessing you had the root mounted read/write. You *really* don't want to be doing that - even >on test systems, remount as r/w only for the time you need it (say for mkdir). > >zFS has had its share of latch contension issues, but I'd lean toward it attempting recovery. > >Shane ... > > >On Sat, May 22nd, 2010 at 9:43 PM, "R.S." <r.skoru...@bremultibank.com.pl> wrote: > >> However, possibly after some "unclean" system close (this is sandbox >> >> system) I had serious problems with IPL. OMVS could not initialize >> for approx. 50 minutes. I guess during the time a checking of ZFS >> structures had a place. A loooong time. Imagine you have to restart your >> production >> system after some (i.e. power) failure. And you have more filesystems >> than ROOT. DUe to lack of OMVS no TCPIP communication was possible. >> Only console and (AFAIR) non-SNA terminals. > >---------------------------------------------------------------------- >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
