John, Thanks so much. This is probably what I need to do. I will add this to my notes file on UNIX commands.
Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of John McKown > Sent: Monday, September 22, 2008 4:56 PM > To: [email protected] > Subject: Re: Space errors in JAVA during SMP/E Apply > > On Mon, 22 Sep 2008 16:48:38 -0400, Lizette Koehler > <[EMAIL PROTECTED]> wrote: > > >I should have mentioned that my zfsadm module is broken. The > /usr/bin/zfsadm is corrupted. The one in my service directory is fine, > but > the one in my production omvs root data set is un unusable. > > > >That is why I was looking for a way to copy the current JV390 file > into a > new JV390.NEW file. > > > >Since I seem to have everything in place, I am not sure why I cannot > grow > this aggr unless it is due to the zfsadm being broken. > > > >Lizette > > > > 1. Fix zfsadm as soon as you can. > > 2) define your new JV390 file with the new size. > > 3) create a new mountpoint for it, say /usr/lpp/jdk.new > > 4) mount it, say as /usr/lpp/jdk.new > > 5) su - (go to root) > > 6) cd /usr/lpp/jdk #current JDK mount point. > > 7) pax -rw -pe * /usr/lpp/jdk.new #copy to new > > 8) unmount /usr/lpp/jdk > > 9) unmount /usr/lpp/jdk.new > > 10) ALTER old.jdk.LDS.name some.new.name.just.to.be.safe > > 11) ALTER new.jdk.LDS.name old.jdk.LDS.name > > 12) mount /usr/lpp/jdk #mount copy of filesystem at old mount point > > === > > The above is off the top of my head, but should be close. I think. > Maybe. YMMV. > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
