All, We have for the longest time used a 256MB TFS for /tmp. Beauty of that is with every IPL, the transient data is wiped out, and start fresh again. We've very rarely ever run into filesystem space problems. However, our DB2 sysprogs are running into problems when performing maintenance activities on our IDAA appliances when loading new/updated code to it via their gui interface. Seems as though that tool wants to use /tmp space between copying data from DB2 filesystem to IDAA hardware. Some of these objects are 2G or larger in size, so they have run into space problems, and they claim there is no way to override what to use for temp space.
So, I've been contemplating making /tmp a standard ZFS of sufficient size, but am wondering how you all setup controls to manage the space? I'm aware of skulker and can schedule it to run daily to clean up the garbage for stuff not accessed for a set period of time, but what do you do about the various stderr, stdout, pid files for IPL time tasks that are still running, that also fit that criteria? Is it ok to delete that stuff while those tasks are still running? -rwxrwxr-x 1 P0SJR SUDOGRP 0 Oct 21 08:43 /tmp/SMPE2015294084338856637/inventory -rwxrwxr-x 1 P0SJR SUDOGRP 150720 Oct 26 08:40 /tmp/SMPE2015299084013259104/inventory -rw-r--r-- 1 P0SJR SUDOGRP 110 Oct 18 03:06 /tmp/TCPIP.Pagent.tmp crw-rw---- 1 P0SJR SUDOGRP 6, 0 Oct 18 03:06 /tmp/dpi_socket -rw-rw---- 1 P0SJR SUDOGRP 87 Oct 18 03:06 /tmp/omproute.stderr -rw-rw---- 1 P0SJR SUDOGRP 0 Oct 18 03:06 /tmp/omproute.stdout -rw-r--r-- 1 P0SJR SUDOGRP 7 Oct 18 03:06 /tmp/pagent.pid -rwx------ 1 P0SJR SUDOGRP 63 Oct 18 03:06 /tmp/sshd.stderr crwxrwxrwx 1 P0SJR SUDOGRP 6, 0 Oct 18 03:06 /tmp/unix.str _________________________________________________________________ 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 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
