RE: Something is eating our disk space

I've used that and it has not shown anything new unfortunately.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Bryan Dietz
Sent: Wednesday, March 30, 2022 8:14 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Something is eating our disk space

just FYI, I believe IBM has shut down most FTP links.
the link mentions QRYIFSLIB, which can be found:
https://public.dhe.ibm.com/services/us/igsc/cs2/ApiSamples/
the savf is named IFSTOOL

<snip>
QRYIFSLIB V1.11.2:
Invalid number of arguments.
Dump stat info for each ifs object into outfile
QRYIFSLIB and, if \A option is selected, QRYIFSLIBA.
- This will not follow symlinks.
- The output file is overwritten on each call.
This utility is unsupported and provided on an as is
basis. Comments can be sent to ddilling@xxxxxxxxxx.

CALL QRYIFSLIB '[path/]*|file' ['\S'] ['\A'] ['\L:lib']
['\Q'] ['\X:names']

[path/] Absolute or relative path ending with a '/'.
* Process all files in a directory.
file Process only specified file system object.
\S Process all subdirectories.
\A Include native authority information.
\L:lib Library to write output files into (Default is QGPL).
\Q Skip /QSYS.LIB
\X:names
Comma delimited list of directory names to exclude
where one directory name can be the special value
*NONLOCAL. *NONLOCAL is a wildcard for the following IBM
supplied directories:
/QSYS.LIB,/QNTC,/QOPT,/QDLS,
/QNetWare,/QLANSrv,/QfileSvr.400


Examples:
CALL PGM(QRYIFSLIB) PARM('/ddilling/myfile.txt' '\A')
CALL PGM(QRYIFSLIB) PARM('/ddilling/*')
CALL PGM(QRYIFSLIB) PARM('/ddilling/*' '\s')
CALL PGM(QRYIFSLIB) PARM('/*' '\s' '\X:*NONLOCAL,/ddilling')


Example queries:
Total size of each directory (non-cumlative)
select DIRNAME, count(*) as "Number of Objects",
sum( cast(st_size as DEC(31) )) as "File Size",
sum( cast(st_allocsz as DEC(31) )) as "Allocated Size"
from QGPL/QRYIFSLIB group by DIRNAME
Total size of root directory (cumlative)
select count(*) as "Number of Objects",
sum( cast(st_size as DEC(31) )) as "File Size",
sum( cast(st_allocsz as DEC(31) )) as "Allocated Size"
from QGPL/QRYIFSLIB
Total size by owner
select ST_UID, count(*) as "Number of Objects",
sum( cast(st_size as DEC(31) )) as "File Size",
sum( cast(st_allocsz as DEC(31) )) as "Allocated Size"
from QGPL/QRYIFSLIB group by ST_UID
order by 3 desc
Show native os400 authorities for each object:
select * from qgpl/qryifslib a left outer join
qgpl/qryifsliba b on a.ST_INO = b.ST_INO

Alan Shore via MIDRANGE-L wrote on 3/30/2022 12:42 PM:

Came across this web site
It may prove useful
What is eating my IFS? -
PowerWire.eu<https://powerwire.eu/what-is-eating-my-ifs>


Alan Shore
Solutions Architect
IT Supply Chain Execution

[NHScsignaturelogo]

60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx

'If you're going through hell, keep going.'
Winston Churchill

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Filip Drzewiecki via MIDRANGE-L
Sent: Wednesday, March 30, 2022 1:33 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Filip Drzewiecki <fdrzewiecki@xxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] RE: Something is eating our disk space

It was run today:
Information collection start . . . . . . : 30/03/22 10:16:56

User libraries 55.35 1098865.44
User directories 30.86 612665.26

User directories has grown from 18% to 30% and I can't find what exactly I mean which folders/files.

-----Original Message-----
From: MIDRANGE-L
<midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@lists
.midrange.com>> On Behalf Of Rob Berendt
Sent: Wednesday, March 30, 2022 7:13 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: RE: Something is eating our disk space

I meant run RTVDSKINF.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104 Ft. Wayne, IN 46818 Ship to:
7310 Innovation Blvd, Dock 9C Ft. Wayne, IN 46818
http://www.dekko.com<http://www.dekko.com>

-----Original Message-----
From: MIDRANGE-L
<midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@lists
.midrange.com>> On Behalf Of Rob Berendt
Sent: Wednesday, March 30, 2022 1:12 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: RE: Something is eating our disk space

If you look at the report generated by PRTDSKINF, is the date/time in "Information collection start . . . . . . :" recent? If not, that would explain why there is a discrepancy. Rerun RTVDIRINF then.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104 Ft. Wayne, IN 46818 Ship to:
7310 Innovation Blvd, Dock 9C Ft. Wayne, IN 46818
http://www.dekko.com<http://www.dekko.com>

-----Original Message-----
From: MIDRANGE-L
<midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@lists
.midrange.com>> On Behalf Of Filip Drzewiecki via MIDRANGE-L
Sent: Wednesday, March 30, 2022 12:49 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Cc: Filip Drzewiecki
<fdrzewiecki@xxxxxxxxxxxxxxxxx<mailto:fdrzewiecki@xxxxxxxxxxxxxxxxx>>
Subject: Something is eating our disk space

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Hi,

I think I have stuck and I need some help.
PRTDISKINFO is showing that 30% of our 2TB disk is eaten by "User Directories".
This is almost 600 Gigs.
I've used few different methods (old IFSTOOLS, running call qsrsrv parm("METRICS" '/' "EPFS") and RTVDIRINF and all of those shows like 65 Gb of files.
I've checked '/tmp' and some other directories and can't find what is eating all that space.

I have not tried yet object_statistics as it was taking ages, I could not figure out how to optimize it.


Filip
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To
subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.m
idrange.com/mailman/listinfo/midrange-l>
or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@lists.
midrange.com> Before posting, please take a moment to review the
archives at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com<https://amazon.midrange.com>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To
subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.m
idrange.com/mailman/listinfo/midrange-l>
or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@lists.
midrange.com> Before posting, please take a moment to review the
archives at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com<https://amazon.midrange.com>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To
subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.m
idrange.com/mailman/listinfo/midrange-l>
or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@lists.
midrange.com> Before posting, please take a moment to review the
archives at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com<https://amazon.midrange.com>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.m
idrange.com/mailman/listinfo/midrange-l>
or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@lists.
midrange.com> Before posting, please take a moment to review the
archives at
https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com<https://amazon.midrange.com>

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com