When you specify the grow command, the size you specify has to be the total of current size+amount to grow by. It’s a little counterintuitive. I've done this too, and wondered why it didn’t work.
So, when you tried this: zfsadm grow ZFS.SYS01.AGG 17120 It should have been zfsadm grow ZFS.SYS01.AGG 14437280 _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 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:[email protected]] On Behalf Of venkat kulkarni Sent: Monday, January 19, 2015 3:04 AM To: [email protected] Subject: Re: ZFS Space issue Hello All, A suggested , I added one more free volume to this ZFS file system and then unmounted and mounted back and after that I issued ZFS grow command to increase file system size but getting below messages # zfsadm aggrinfo ZFS.SYS01.AGG ZFS.SYS01.AGG (R/W COMP): 1712339 K free out of total 14420160 # zfsadm grow ZFS.SYS01.AGG 1440 IOEZ00173I Aggregate ZFS.SYS01.AGG successfully grown ZFS.SYS01.AGG (R/W COMP): 1712339 K free out of total 14420160 # zfsadm aggrinfo ZFS.SYS01.AGG ZFS.SYS01.AGG (R/W COMP): 1712339 K free out of total 14420160 # df -Pk /support/DGPBY Filesystem 1024-blocks Used Available Capacity Mounted on ZFS.SYS01.AGG 14420160 12707821 1712339 89% /support/DGPBY # zfsadm grow ZFS.SYS01.AGG 17120 IOEZ00173I Aggregate ZFS.SYS01.AGG successfully grown ZFS.SYS01.AGG (R/W COMP): 1712339 K free out of total 14420160 # df -Pk /support/DGPBY Filesystem 1024-blocks Used Available Capacity Mounted on ZFS.SYS01.AGG 14420160 12707821 1712339 89% /support/DGPBY # zfsadm grow ZFS.SYS01.AGG 144201 IOEZ00173I Aggregate ZFS.SYS01.AGG successfully grown ZFS.SYS01.AGG (R/W COMP): 1712339 K free out of total 14420160 # I am not sure, why size is not getting increased or I am missing something. On Sat, Jan 17, 2015 at 6:24 AM, John McKown <[email protected]> wrote: > Which is why I use a DATACLAS which has a DYNVOL value > 0 assigned to it. > I think that DYNVOL is the proper variable. > On Jan 16, 2015 6:27 PM, "Lizette Koehler" <[email protected]> > wrote: > > > Chapter 4 "Creating and managing zFS file systems using > > compatibility > mode > > aggregates" in Distributed File Service zFS Administration states: > > > > if an ALTER ADDVOLUMES is done to a data set already opened and > allocated, > > the data set must be closed, unallocated, reallocated, and reopened > before > > VSAM can extend onto the newly added candidate volume. > > For zFS, this means that if the zFS aggregate is already attached > > when > the > > ALTER ADDVOLUMES is done, it must be detached and attached again > > before > zFS > > can extend to the newly added candidate volume. Compatibility mode > > aggregates must be unmounted and mounted again (because that is when > > they are detached and attached). You can use the remount capability > > of z/OS UNIX. For details, see the topic on Remounting a mounted > > file system in z/OS UNIX System Services Planning. > > > > > > > > Lizette > > > > -----Original Message----- > > >From: venkat kulkarni <[email protected]> > > >Sent: Jan 16, 2015 11:19 AM > > >To: [email protected] > > >Subject: Re: ZFS Space issue > > > > > >Thanks Lizette, But after this alter command, I am not able to > understand > > >dismount and mount action need to be taken to make sure that its in > > affect. > > > > > >Can you please explain this. once. > > > > > >On Fri, Jan 16, 2015 at 10:23 PM, Lizette Koehler < > > [email protected]> > > >wrote: > > > > > >> Yes the alter command will do what you request. But review what > others > > >> have stated about dismount/mount actions. > > >> > > >> Lizette > > >> > > >> > > >> -----Original Message----- > > >> From: IBM Mainframe Discussion List > > >> [mailto:[email protected]] > > On > > >> Behalf Of venkat kulkarni > > >> Sent: Friday, January 16, 2015 9:35 AM > > >> To: [email protected] > > >> Subject: Re: ZFS Space issue > > >> > > >> Hello Lizette, Yes. As you rightly said, ZFS dataset should grow > > >> by > its > > >> own when it reaches to threshold but in my case, this ZFS file > > >> system > is > > >> part of two volume and both are 99% full, So I dont think the > > possibility > > >> of growing it further. > > >> > > >> But the solution for this problem, I was thinking that to add one > > >> more volume to this ZFS dataset using > > >> > > >> tsocmd "ALTER 'ZFS.SYS01.AGG.DATA' ADDVOLUMES(*)" command, So now > > this > > >> ZFS will be part of 3 multi volume and then it can grow its own, > > >> as it will find enough free space in defined volume. > > >> > > >> Please suggest . > > >> > > >> On Fri, Jan 16, 2015 at 9:55 PM, Lizette Koehler < > > [email protected]> > > >> wrote: > > >> > > >> > Just be careful with manual effort with zFS files. They are > > >> > linear VSAM datasets. Unless you have a need to control the > > >> > volumes, the > zFS > > >> > can grow itself. So long as the volume and pool has sufficient > > >> > storage you should be okay. > > >> > > > >> > Do you see any IOE messages in SYSLOG for this zFS file? If > > >> > so, I would use that as a guideline. > > >> > > > >> > Questions for your user(you do not need to post answers to > > >> > these > > >> > questions): > > >> > > > >> > Some users think of zFS like on open system - I would check > > >> > with the user to find out why they need more space. > > >> > if this file has not been closed and opened in a while the High > > >> > Used/High Alloc may not be 100% Accurate. But this file is > currently > > >> > at > > >> > 14,766,243,840 or 14GB. This is a huge file. If a mod9 is > > >> > ~8GB > this > > >> > is almost the size of 2 mod9s. > > >> > Does the file grow quickly or slowly? 81% used is not > > >> > necessarily > bad > > >> > How does it grow - Daily/Weekly/Monthly/etc.? > > >> > What monitoring is available for this zFS? Is there automation > > >> > to notify when it is full or getting full? > > >> > What is the estimate on the size of the file over time? > > >> > What type of clean-up or archive is being done on this file? > > >> > > > >> > > > >> > > > >> > It has EA/EF on it, that is good. However, it also means that > > >> > it > will > > >> > always grow. Does your user have an archive or clean-up process? > If > > >> > not, you could be always adding storage. > > >> > > > >> > I have seen zFS files grow but after looking at it with the > customer, > > >> > it turned out they had some clean-up they could do and it > > >> > reduced > the > > >> > file significantly. They had old log files in the zFS that > > >> > could be deleted. I have another customer who requested their > > >> > zFS to not > have > > >> > EA/EF so it would fail at 4GB. And yet another customer that > > >> > has a really huge zFS that is normal. So it will depend on > > >> > your shop and > > the > > >> needs of the application. > > >> > > > >> > If everything is normal and they need the storage, then just > > >> > make > sure > > >> > they have a dataclas on it that has candidate volumes so you do > > >> > not have to manually add to the file. > > >> > > > >> > Check the IOE and IEC message in SYSLOG for your zFS. They > > >> > will provide the information you need to handle the needs of zFS. > > >> > > > >> > Lizette > > >> > > > >> > > > >> > -----Original Message----- > > >> > From: IBM Mainframe Discussion List [mailto: > [email protected]] > > >> > On Behalf Of venkat kulkarni > > >> > Sent: Friday, January 16, 2015 9:03 AM > > >> > To: [email protected] > > >> > Subject: Re: ZFS Space issue > > >> > > > >> > Thanks for reply. Both ABD076 and ABD077 volume, which is part > > >> > of > this > > >> > ZFS file systems are 99% full. But I have 1 more volume, with > > >> > enough free space in this same storage group. So, my aim is to > > >> > increase > space > > >> > for this ZFS file system. > > >> > Data Set Information Command ===> > > >> > > > More: > > >> > + > > >> > Data Set Name . . . . : ZFS.SYS01.AGG.DATA > > >> > > > >> > General Data Current Allocation > > >> > Management class . . : **None** Allocated cylinders : > 20,028 > > >> > Storage class . . . : **None** Allocated extents . : 2 > > >> > Volume serial . . . : ABD076 + > > >> > Device type . . . . : 3390 > > >> > Data class . . . . . : **None** > > >> > Organization . . . : VS Current Utilization > > >> > Record format . . . : ? Used cylinders . . : ? > > >> > Record length . . . : ? Used extents . . . : ? > > >> > Block size . . . . : ? > > >> > 1st extent cylinders: 10014 > > >> > Secondary cylinders : 0 Dates > > >> > Data set name type : EXTENDED Creation date . . . : > > 2007/02/25 > > >> > Referenced date . . : > > 2014/12/18 > > >> > Expiration date . . : > > >> > ***None*** > > >> > > > >> > > > >> > LISTCAT command output > > >> > CLUSTER ------- ZFS.SYS01.AGG > > >> > IN-CAT --- CATALOG.SMS > > >> > HISTORY > > >> > *** > > >> > DATASET-OWNER-----(NULL) CREATION--------2007.056 > > >> > RELEASE----------------2 EXPIRATION------0000.000 > > >> > SMSDATA > > >> > STORAGECLASS ------ZFSSC MANAGEMENTCLASS----ZFSMC > > >> > DATACLASS ---------ZFSDC LBACKUP ---0000.000.0000 > > >> > EATTR-------------(NULL) > > >> > BWO STATUS------00000000 BWO TIMESTAMP---00000 > 00:00:00.0 > > >> > BWO---------------(NULL) > > >> > RLSDATA > > >> > LOG ----------------(NULL) RECOVERY REQUIRED --(NO) > > FRLOG > > >> > -------- > > >> > ----(NULL) > > >> > VSAM QUIESCED -------(NO) RLS IN USE ---------(NO) > > >> > LOGREPLICATE-- > > >> > -----------(NO) > > >> > LOGSTREAMID-----------------------------(NULL) > > >> > RECOVERY TIMESTAMP LOCAL-----X'0000000000000000' > > >> > RECOVERY TIMESTAMP GMT-------X'0000000000000000' > > >> > PROTECTION-PSWD-----(NULL) RACF----------------(NO) > > >> > ASSOCIATIONS > > >> > DATA-----ZFS.SYS01.AGG.DATA > > >> > DATA ------- ZFS.SYS01.AGG.DATA > > >> > IN-CAT --- CATALOG.SMS > > >> > HISTORY > > >> > DATASET-OWNER-----(NULL) CREATION--------2007.056 > > >> > *** > > >> > RELEASE----------------2 EXPIRATION------0000.000 > > >> > ACCOUNT-INFO-----------------------------------(NULL) > > >> > PROTECTION-PSWD-----(NULL) RACF----------------(NO) > > >> > ASSOCIATIONS > > >> > CLUSTER--ZFS.SYS01.AGG > > >> > ATTRIBUTES > > >> > KEYLEN-----------------0 AVGLRECL---------------0 > > >> > BUFSPACE------ > > >> > ------8192 CISIZE--------------4096 > > >> > RKP--------------------0 MAXLRECL---------------0 > > >> > EXCPEXIT------ > > >> > ----(NULL) CI/CA----------------180 > > >> > STRIPE-COUNT-----------1 > > >> > SHROPTNS(2,3) RECOVERY UNIQUE NOERASE > > LINEAR > > >> > NOWRITECHK UNORDERED NOREUSE > > >> > NONSPANNED EXTENDED EXT-ADDR ZFS > > >> > STATISTICS > > >> > REC-TOTAL--------------0 SPLITS-CI--------------0 > > >> > EXCPS--------- > > >> > ---------0 > > >> > REC-DELETED------------0 SPLITS-CA--------------0 > > >> > EXTENTS------- > > >> > ---------2 > > >> > REC-INSERTED-----------0 FREESPACE-%CI----------0 > > >> > SYSTEM-TIMESTA > > >> > MP: > > >> > REC-UPDATED------------0 FREESPACE-%CA----------0 > > >> > X'0000000 > > >> > 000000000' > > >> > *** REC-RETRIEVED----------0 FREESPC----------------0 > > >> > ALLOCATION > > >> > SPACE-TYPE------CYLINDER HI-A-RBA-----14766243840 > > >> > SPACE-PRI----------10014 HI-U-RBA-----14766243840 > > >> > SPACE-SEC--------------0 > > >> > VOLUME > > >> > VOLSER------------ABD076 PHYREC-SIZE---------4096 > > >> > HI-A-RBA------ > > >> > 7383121920 EXTENT-NUMBER----------1 > > >> > DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 > > >> > HI-U-RBA------ > > >> > 7383121920 EXTENT-TYPE--------X'40' > > >> > VOLFLAG------------PRIME TRACKS/CA-------------15 > > >> > EXTENTS: > > >> > LOW-CCHH-----X'00030000' LOW-RBA----------------0 > > >> > TRACKS-------- > > >> > ----150210 > > >> > HIGH-CCHH----X'2720000E' HIGH-RBA------7383121919 > > >> > VOLUME > > >> > VOLSER------------ABD077 PHYREC-SIZE---------4096 > > >> > HI-A-RBA-----1 > > >> > 4766243840 EXTENT-NUMBER----------1 > > >> > DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 > > >> > HI-U-RBA-----1 > > >> > 4766243840 EXTENT-TYPE--------X'40' > > >> > VOLFLAG------------PRIME TRACKS/CA-------------15 > > >> > EXTENTS: > > >> > LOW-CCHH-----X'00030000' LOW-RBA-------7383121920 > > >> > TRACKS-------- > > >> > *** > > >> > ----150210 > > >> > HIGH-CCHH----X'2720000E' HIGH-RBA-----14766243839 > > >> > *** > > >> > * > > >> > > > >> > > > >> > On Fri, Jan 16, 2015 at 8:23 PM, Lizette Koehler > > >> > <[email protected]> > > >> > wrote: > > >> > > > >> > > What data class do you have assigned to this zFS? Does it > > >> > > have > DYNA > > >> > > VOL Count or Vol Count? > > >> > > > > >> > > You should not need to add unless there are errors indicating > > >> > > an > out > > >> > > of space condition. SYSLOG should have an IEC161 message > > >> > > about > it. > > >> > > > > >> > > Is this file set up for EA/EF (Extended Addressable/Extended > > Format)? > > >> > > If not, it will only get to 4G before it will fail. > > >> > > > > >> > > When you do a LISTC ENT(name) against this zFS does the > information > > >> > > on the VOLUME section show one volume or volumes with * in > > >> > > the > > field? > > >> > > > > >> > > With aggrow setup - this is just informational and not an issue. > > >> > > zFS will expand the file until it hits 4GB unless it is > > >> > > defined > with > > >> EA/EF. > > >> > > > > >> > > > > >> > > Lizette > > >> > > > > >> > > -----Original Message----- > > >> > > From: IBM Mainframe Discussion List > > >> > > [mailto:[email protected]] On Behalf Of venkat > > >> > > kulkarni > > >> > > Sent: Friday, January 16, 2015 12:54 AM > > >> > > To: [email protected] > > >> > > Subject: ZFS Space issue > > >> > > > > >> > > Hello, > > >> > > User want me to increase size for this , as it filled by 81%. > > >> > > But when I checked, this dataset is multi volume and both > > >> > > volume are almost full. So, now what alternative do I have to > > >> > > increase the > size > > >> > > of this ZFS file system . This is SMS managed dataset and in > > >> > > this storage group, I have one volume which is 85% full and > > >> > > rest all > are > > >> 99%. > > >> > > > > >> > > # df -Pk /support/DGPBY > > >> > > Filesystem 1024-blocks Used Available Capacity > > Mounted > > >> > on > > >> > > > > >> > > ZFS.SYS01.AGG 14420160 11597365 2822795 81% > > >> > /support/DGPBY > > >> > > # > > >> > > > > >> > > Any suggestion. > > >> > > > > > > -------------------------------------------------------------------- > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO > > IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] 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 [email protected] with the message: INFO IBM-MAIN
