I received this find command from an IBMer (Bill Schoen maybe). It will
list all of the files and directories contained in a physical HFS/zFS.
It only lists objects within a single MVS dataset. I use it to determine
who is using space within my root HFS:
The command I have come up with is:
Thanks everyone for your help. We found some logs from z/Oses HTTP
server that were dumping into our root file system. Problem resolved
(for now).
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Klein, Kevin
Sent: Monday, July 14, 2008 1:59
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Klein, Kevin
Sent: Tuesday, July 15, 2008 9:35 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Unix System Services File Space Used
Thanks everyone for your help. We found some logs from z
On Tue, 15 Jul 2008 09:35:06 -0500, Klein, Kevin [EMAIL PROTECTED] wrote:
Thanks everyone for your help. We found some logs from z/Oses HTTP
server that were dumping into our root file system. Problem resolved
(for now).
Just one of several good reasons to mount your root as read only.
Mark
Try /usr/lpp/tcpip/samples/rmoldlogs
snip
Ouch. For everything that creates a log, I put that in its own private
filesystem. Really helps, given how infrequently I remember to purge the
logs. I'm going to automate that some day.
/snip
21:08
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Unix System Services File Space Used
Try /usr/lpp/tcpip/samples/rmoldlogs
snip
Ouch. For everything that creates a log, I put that in its own private
filesystem. Really helps, given how infrequently I remember to purge the
logs. I'm going to automate
Yes, route your logs into a separate file system, and roll your logs. Look
at the Logging and Reports section of Appendix B. Configuration
directives for the HTTP server. Lots of good stuff. The only problem I
ever had with the logging is that you have to have reporting turned on for
the
du -sk * from / should give you a list of the directories under /.
You can then drill down into the offenders to see where the space is
being taken.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Klein, Kevin
Sent: Monday, July 14, 2008 1:59
I'd use du -k to find the problem directories and then zero in on them.
If you're running HTTP server, look at the log and error files directory.
Also, /usr/spool can get big if not trimmed regularly.
Robert
--
For IBM-MAIN
On Mon, 14 Jul 2008 13:59:08 -0500, Klein, Kevin [EMAIL PROTECTED] wrote:
We have a zFS file at 4GB so it can't expand. It happens to be our root
file system and it's full so I'm not able to create any more directories
off the root. We don't think we should have 4GB of data on this file.
Is
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark
Zelden
Sent: 14. heinäkuuta 2008 23:48
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Unix System Services File Space Used
On Mon, 14 Jul 2008 13:59:08 -0500, Klein
You can define it as extended format so it can expand past 4GB limit.
Mark Jacobs
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Klein, Kevin
Sent: Monday, July 14, 2008 2:59 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Unix System Services File
12 matches
Mail list logo
