On Wed, Aug 28, 2002 at 03:44:36PM -0400, Gene Heskett wrote:
> On Wednesday 28 August 2002 15:13, Amy Tanner wrote:
> >On Wed, Aug 28, 2002 at 02:30:41PM -0400, Gene Heskett 
> >etimeout 300
> 
> Which looks like enough, but note on down the page where it 
> indicates it took 7 minutes, not 5.

Careful.  Estimate timeout is per client, not per disklist entry, and
is (etimeout * number_of_disklist_entries).  So if you have a client
box1, and box1 has three disklist entries, then the real wall-clock
estimate timeout for box1 would be 300*3 = 15 minutes

> >                          Total       Full      Daily
> >                        --------   --------   --------
> >Estimate Time (hrs:min)    0:07
> >Run Time (hrs:min)         9:33
> >Dump Time (hrs:min)        8:30       6:20       2:11
> >Output Size (meg)       15258.3    10167.3     5091.0
> >Original Size (meg)     15258.3    10167.3     5091.0
> >Avg Compressed Size (%)     --         --         --   
> > (level:#disks ...) Filesystems Dumped           71         20    
> >     51   (1:43 2:6 3:2) Avg Dump Rate (k/s)       510.3     
> > 457.0      665.0
> >
> >Tape Time (hrs:min)        1:54       1:21       0:33
> >Tape Size (meg)         15260.5    10167.9     5092.6
> >Tape Used (%)              46.6       31.0       15.5  
> > (level:#disks ...) Filesystems Taped            71         20    
> >     51   (1:43 2:6 3:2) Avg Tp Write Rate (k/s)  2284.3    
> > 2151.3     2606.0
> 
> This doesn't add up, you're moving about 2.2 megs/second, and it 
> takes over 8 hours?

2.2 megs/second is *taper* throughput, not *dumper* throughput.

-- 
Jay Lessert                               jay_lessert AT accelerant DOT net
Accelerant Networks Inc.                       (voice)1.503.439.3461
Beaverton OR, USA                                (fax)1.503.466.9472