Carl,

Both things already suggested (turning on the file close logging events and
using FILERPT) are good as far as they go.  For some years now, though, not
all I/O's to files have been logged in the system log files.  Only those
I/O's that go through the file system are actually logged.  Memory-mapped
I/O's are not.  Unfortunately for what you are trying to do (but very
fortunately for you, and the rest of us, who desire good disk I/O
performance) the lion's share (or at least "a whole lot") of I/O's
performed on your system during the course of a day are likely to bypass
the file system altogether.

You will just have to rely more heavily on your knowledge of the
application that any tool available, or likely to be available for some time.

Bill

At 07:57 AM 8/3/99 -0500, Carl McNamee wrote:
>I have some private volumes that have one or two disks getting hit very hard
>and the other disks just kind off sitting idle.  I was hoping to work with
>our developement staff to spread the files so that the heaviest hit files
>are spread better.
>
>The more I think about it I guess what I really need to know is which files
>are hit heaviest.  Do you know of any utilities that can help with this?
>
>Carl
>
>-----Original Message-----
>From: Mike Hornsby [mailto:[log in to unmask]]
>Sent: Monday, August 02, 1999 6:39 PM
>To: [log in to unmask]
>Subject: finding the extents of a files or files
>
>
>
>Carl,
>
>Sorry, from your email I thought that you were interested in a single file.
>
>Just out of curiosity, what issue or problem are you attempting to resolve?
>
>Mike Hornsby
>
>CoFounder/CTO
>
>Beechglen Development Inc.
>
>www.beechglen.com
>
>beechglen.com (3000 with sample weblications)
>
>