Amanda-Users

Re: hitting EOT early?

2007-10-17 11:12:26
Subject: Re: hitting EOT early?
From: Nick Brockner <nbrockne AT hamilton DOT edu>
To: Paul Bijnens <Paul.Bijnens AT xplanation DOT com>
Date: Wed, 17 Oct 2007 08:05:05 -0400
Thanks, I just did a "mt -f /dev/st0 compression 0", "defcompression 0" didn't seem to be valid for this device (or nst0), so I guess I'll just reboot to be sure compression is off on the drive.

I guess we'll see what happens tonight.

Nick
Paul Bijnens wrote:
On 2007-10-16 16:18, Nick Brockner wrote:
Hi All,

I am using amanda 2.5.1p1, and I have just started seeing this (with the failing of the DLE that is currently on):

planner: Last full dump of <HOSTNAME1>:/home on tape overwritten in 1 run. taper: tape weekly-2/tape-3 kb 30827264 fm 28 writing file: No space left on device taper: retrying <HOSTNAME2>:/.0 on new tape due to: [writing file: No space left on device]
  taper: tape weekly-2/tape-6 kb 0 fm 0 [OK]

I am using DAT72, so I should be getting 36 G of usable space. Please help, as I can't get the spanning to work either, and when it tries to write to the next tape, it just dies for some reason. . .


I bet you are using the tape drive in hardware compression mode
and have Amanda let the data compress with software compression
as well.

The compression algorithm in DAT drives is stupid enough to not
detect uncompressable data, and hence blindly applying that compression
algorith to such data results in actually expanding the data by
about 20-30%.  That should acount for getting 30GB instead of 36 GB
data on the tape.

Solution:  disable the hardware compression on the tape drive.

http://wiki.zmanda.com/index.php/Hardware_compression




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