Amanda-Users

Re: Problem with compression?

2003-02-21 19:33:34
Subject: Re: Problem with compression?
From: Gene Heskett <gene_heskett AT iolinc DOT net>
To: John Oliver <joliver AT john-oliver DOT net>, amanda-users AT amanda DOT org
Date: Fri, 21 Feb 2003 18:14:37 -0500
On Fri February 21 2003 14:51, John Oliver wrote:
>I got this report from amanda.  It looks to me like it's reporting
> that it used 48.9% of the tape (a DLT 4000 20/40GB), but that it
> ran out of space.
>
>
>These dumps were to tape Indyme008.
>*** A TAPE ERROR OCCURRED: [[writing file: No space left on
> device]]. Some dumps may have been left in the holding disk.
>Run amflush to flush them to tape.
>The next tape Amanda expects to use is: Indyme009.
>
>FAILURE AND STRANGE DUMP SUMMARY:
>  backup     /dev/hda1 lev 1 FAILED [out of tape]
>  backup     /dev/hda1 lev 1 FAILED [dump to tape failed]
>
>
>STATISTICS:
>                          Total       Full      Daily
>                        --------   --------   --------
>Estimate Time (hrs:min)    0:04
>Run Time (hrs:min)         6:40
>Dump Time (hrs:min)        1:58       1:56       0:02
>Output Size (meg)        9737.1     9611.4      125.7
>Original Size (meg)     19162.4    19028.8      133.6

Humm, if thats a 40gig tape (with compression) it would be about a 
20 gigger without.  And if hardware compression is also enabled, it 
would not be unusual to over-run the EOT because the compressed 
stuff you are sending it will usually expand some, often 15 to 20% 
in going thru the hardware compressor too.

Throw in that marketing is usually a bit optimistic in saying its a 
20 gigger without compression, and that always needs a fudge factor 
when actually estimating, and it likely this will happen.

Also, while this doesn't enter into it for me, see the average dump 
rates reported below, how does that compare to the drives rated 
speed at its compression state?  If that drive is faster then the 
data comeing in, it will write null blocks for a bit waiting on 
data, and this wastes space.  Could be a pretty good percentage 
under the right conditions, like no, or too small a holding disk.

>Avg Compressed Size (%)    50.8       50.5       94.1  
> (level:#disks ...)
>Filesystems Dumped           18         17          1   (1:1)
>Avg Dump Rate (k/s)      1406.6     1412.5     1068.3
>
>Tape Time (hrs:min)        1:56       1:55       0:01
>Tape Size (meg)          9738.0     9612.2      125.8
>Tape Used (%)              48.9       48.2        0.6  
> (level:#disks ...)
>Filesystems Taped            18         17          1   (1:1)
>Avg Tp Write Rate (k/s)  1427.5     1427.3     1438.5
>
>
>NOTES:
>  planner: Incremental of tgs-2:/dev/hda2 bumped to level 3.
>  planner: Incremental of devdist:/dev/hda2 bumped to level 2.
>  planner: Incremental of qaweb:/dev/hdc2 bumped to level 2.
>  planner: Full dump of tgs-2:/dev/hda2 promoted from 4 days
> ahead. planner: Full dump of devdb:/dev/hda2 promoted from 4 days
> ahead. planner: Full dump of qaweb:/dev/hdc2 promoted from 4 days
> ahead. planner: Full dump of qadb:/dev/hda2 promoted from 4 days
> ahead. planner: Full dump of devdist:/dev/hda2 promoted from 4
> days ahead. planner: Full dump of devweb:/dev/hda2 promoted from
> 4 days ahead. planner: Full dump of cm:/dev/hda7 promoted from 4
> days ahead. planner: Full dump of qadist:/dev/hda2 promoted from
> 4 days ahead. planner: Full dump of proddist:/dev/hda2 promoted
> from 4 days ahead. planner: Full dump of proddb:/dev/sda2
> promoted from 5 days ahead. planner: Full dump of
> qacoll:/dev/hda2 promoted from 5 days ahead. planner: Full dump
> of devcoll:/dev/hdc2 promoted from 5 days ahead. planner: Full
> dump of qaall:/dev/hdc2 promoted from 5 days ahead. planner: Full
> dump of prodweb:/dev/sda2 promoted from 5 days ahead. planner:
> Full dump of cm:/dev/hda5 promoted from 5 days ahead. planner:
> Full dump of cm:/dev/hda3 promoted from 5 days ahead. planner:
> Full dump of cm:/dev/hda1 promoted from 5 days ahead. taper: tape
> Indyme008 kb 20040128 fm 19 writing file: No space left on device
>  driver: dumper0 pid 28624 is messed up, ignoring it.
>  driver: dumper0 exited with signal 9
>
>
>DUMP SUMMARY:
>                                     DUMPER STATS            TAPER
> STATS HOSTNAME     DISK        L ORIG-KB OUT-KB COMP% MMM:SS 
> KB/s MMM:SS KB/s
>-------------------------- ---------------------------------
>------------
>backup       /dev/hda1   1 FAILED
>---------------------------------------
>cm           /dev/hda1   0    4770   2720  57.0   0:04 604.5
>0:031055.0
>cm           /dev/hda2   1  136810 128800  94.1   2:011068.3
>1:301438.5
>cm           /dev/hda3   0  401740 315040  78.4   2:501853.7
>3:411425.5
>cm           /dev/hda5   0   81950  26272  32.1   0:211239.8
>0:241117.2
>cm           /dev/hda7   0   62900  20096  31.9   0:161243.1
>0:151316.8
>devcoll      /dev/hdc2   0  867590 283776  32.7   2:521651.1
>3:151455.1
>devdb        /dev/hda2   0 1143680 334272  29.2   3:171695.0
>3:541426.1
>devdist      /dev/hda2   0  958190 309536  32.3   3:041685.3
>3:371425.0
>devweb       /dev/hda2   0  970370 321056  33.1   3:071718.5
>3:451426.6
>proddb       /dev/sda2   0 1054360 339488  32.2   4:141335.8
>3:581428.7
>proddist     /dev/hda2   0  864620 280992  32.5   6:30 721.1
>3:171423.5
>prodweb      /dev/sda2   0  672850 227424  33.8   3:001261.4
>2:371449.8
>qaall        /dev/hdc2   0  866380 283136  32.7   2:511651.3
>3:191422.3
>qacoll       /dev/hda2   0  867580 283808  32.7   2:571605.4
>3:201421.3
>qadb         /dev/hda2   0 1059160 301600  28.5   3:081603.4
>3:321424.4
>qadist       /dev/hda2   0  866450 282688  32.6   2:551617.6
>3:181427.1
>qaweb        /dev/hdc2   0 1091370 306976  28.1   3:071638.5
>3:361422.7
>tgs-2        /dev/hda2   0 76514805924064  77.4  71:351379.4
>69:061429.0
>
>(brought to you by Amanda version 2.4.3)

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.23% setiathome rank, not too shabby for a WV hillbilly

<Prev in Thread] Current Thread [Next in Thread>