In regard to: Re: [Networker] Slow Performance for large file system -...:

Thanks for the reminder. I had previously install the "trace" utility from 
Legato.
The save process is doing an "lstat" after "lstat" after "lstat" on each of the 
files, it appears, with some hex dumps thrown every so often.
Randy

Ok, so it's stat'ing each inode to check the inode times, to see if the
file needs to be backed up.

Now what you'll need to determine is

- is the interval from one lstat() to the next about the same as it is
  when performance is good (the start of a backup)?

- what directory is it in?  Unless you actually catch it changing
  directories, the easiest way to tell for non-shell processes is using
  something like `lsof' on the save process.

- what does

       defragment -n -v

  report for that domain?

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=