John Hein wrote:
John Hein wrote at 21:38 -0700 on Jan 21, 2009:
> Tom Robinson wrote at 12:30 +1100 on Jan 22, 2009:
> > I've got several disks that are showing weird compression results in the
> > amanda report. Here's one of them:
> >
> > DUMPER STATS TAPER STATS
> > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
> > ------------------------------------
------------------------------------------ ---------------
> > host /disk 1 2031690 4063380 200.0 36:34
1852.3 6:27 10487.2
> >
> >
> > Note the ORIG-KB blows out to twice the size! COMP% is 200.0...
> >
> > This happens on more that one disk actually. I chose this disk as it's
> > the biggest disk that I dump, it shows the most expansive blowout and I
> > noticed it first. This disk uses 'compress NONE' (dumptype is
> > nocomp-root). Some of the other disks showing compression weirdness are
> > using 'compress client fast' in their DLE's.
>
> Smells like a factor of two error somewhere (512 byte blocks vs. 1024?).
> What does 'env -i du -ks /disk' say?
Never mind that last request... your report above shows a level 1, not
0. So du output won't be a useful comparision to the numbers above.
Does it behave the same (x2) for level 0 dumps, too?
The last full run looks like this:
host /disk 0 75564750 108727227 143.9 384:15 4716.0 98:47
18345.1
The thing is, I WAS using compression back then and thought that maybe
it was causing the blowout so turned it off. (I'm yet to run a full dump
on 'compress NONE'). It's not quite x2 but its larger than ORIG-KB.
t.
--
Tom Robinson
System Administrator
MoTeC
121 Merrindale Drive
Croydon South
3136 Victoria
Australia
T: +61 3 9761 5050
F: +61 3 9761 5051
M: +61 4 3268 7026
E: tom.robinson AT motec.com DOT au
| 