Re: IFS Space Utilization Report?

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

One of the Unix dweebs will need to explain more here, I think. 'du' has 
some other switches that have to do with multiple links to an object, 
according to the AIX docs. I did not look too carefully for details.

One thing I like is getting the full path for each object. And the size is 
actual disk allocated space, I believe, instead of bytes.

The symbolic link thing is tricky when walking the IFS tree - different 
functions to get resolved info vs. just link info (lstat vs. stat, right?). 
And one of the APIs lets you filter out symbolic links - nice.

It's still not very efficient, IMO - takes a long time to get through a big 
system. Can you imagine a SAN, with 22 teras?

Regards

Vern

At 04:11 PM 8/19/2003 -0500, you wrote:
> Things to be careful of are symbolic links, etc.  There are a lot of
> these.  You want to ensure that you are reporting the space of the
> symbolic link and not the object it references.
>
> Rob Berendt
> --
>
> Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
>         Subject:        Re: IFS Space Utilization Report?
>
> There's always PASE - call qp2term. 'df' is not there - probably not very
> meaningful on a 400, if I remember what it does. 'du' IS there, and the
> same redirection options are there, of course.
>
> 'du -a' resulted in the following (all files in all subdirectories) -
> numbers on the left are the number of 512-byte blocks. 'du -ak' would list