Am 03.02.2014 15:29, schrieb Jean-Louis Martineau:
> On 01/27/2014 01:35 PM, Stefan G. Weichinger wrote:
>> Do I have to use a specific version of amanda (newer than release X) to
>> make use of pigz?
> 
> I tested 3.3.6 using pigz as a client-compress-custom options and
> amrestore can restore it.
> 
> I don't know exactly what's the problem, so I can't tell you when it was
> fixed.

Sorry to say ... I still see this issue on 2 servers.
My own amanda server runs (current official stable) 3.3.5 ...

I tested (hostname: hiro, config: daily, DLE: pigz) ->

When I amrestore the very same DLE from the holdingdisk (before having
flushed it) it works:

# amrestore --config daily --holding
/mnt/amhold/daily/20140218165332/hiro.oops.intern.pigz.1  hiro pigz

I get the file:

$ file hiro.oops.intern.pigz.20140218165332.1.0000001
hiro.oops.intern.pigz.20140218165332.1.0000001: POSIX tar archive (GNU)

and it is possible to untar it correctly.

I flushed this to tape:

$ amflush -b daily hiro pigz

and tried to restore it:

$ amrestore --config daily /dev/nst0 hiro pigz
Restoring from tape daily04 starting with file 1.
amrestore: 1: restoring split dumpfile: date 20140218165332 host
hiro.oops.intern disk pigz part 1/UNKNOWN lev 1 comp cust program
/bin/tar client_custom_compress /usr/bin/pigz
ERROR: /usr/bin/pigz exited with status 2

What about this error?

The fun part is that I get

hiro.oops.intern.pigz.20140218165332.1.0000001

again!


So it might be some small cosmetic issue?
Maybe you use another version of pigz, JL?

I have pigz 2.3.1 here (gentoo linux).

Maybe some other amanda user feels helpful and wants to test something
similar on his boxes?

Thanks, Stefan

Reply via email to