Discrepancy between ps -i -o inblk and figuring numbers by hand

[Jonathan Stewart]

--- GiGiorgoseKeramidaskekeramidaeceidpupatrasr> wrote:
> On 2005-03-24 19:53, Jonathan Stewart <jojonstew83 at yahoo.com> wrote:
> >--- Dan Nelson <dndnelsonlallantgroupom> wrote:
> >>In the last episode (Mar 24), Jonathan Stewart said:
> >>> In that case how would I track how much information a process has
> >>> actually read from a drive?  I occasionally run processes that
> >>> will read as much as 40+ gig in a single run which takes quite a
> >>> while and on windows :P I can see "bytes read" and "bytes
> written"
> >>> per process which lets me track how much the program has read so
> >>> far and thus get an idea of how close it is to done.  Sorry for
> >>> the run-on sentence there.
> >>
> >> I use lslsofwhich can tell you the file offset of each open
> >> fifiledescriptor "lslsofo -o20 -p ###" will print all the files
> >> currently opened by pipid##, and their current offset.
> >
> > HmHmmthat almost works but the program opens 1000's of files each
> > time.  The program is Unison which is a file synchronizer and I
> have
> > it synchronizing files sets >40GB with and 1000's or more files.
> > Based on your description once the file is closed I can't even tell
> if
> > it was read or not :P
> 
> So, what you are looking for is a single byte count that increases
> sequentially for all read() and write() system calls?
> 
Pretty much, yes. To be specific all read() and write() calls for a
given process.  Even something that counted in 512 byte or UFUFSlocks
would be useful.

Thanks,
Jonathan


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250