Jon LaBadie <jon AT jgcomp DOT com> writes:

> On Wed, Sep 24, 2003 at 01:54:49PM -0500, Deb Baddorf wrote:
> > From a client  machine,  the admin sent me this:
> > 
> > Sep 24 02:45:32 daesrv /kernel: pid 7638 (gzip), uid 2: exited on signal 11 
> > (core dumped)
> > 
> > The above message shows gzip crashed on daesrv last night.  It crashed
> > because there is a hardware problem on that machine, but since it was
> > probably part of an amanda backup that did not work as expected, I wanted
> > to be sure amanda had reported something about it to you.   -client admin
> > 
> > Amanda herself had reported a strange error in her mail report:
> > 
> > daesrv.fna /usr lev 0 STRANGE
> > .....
> > | DUMP: 33.76% done, finished in 1:20
> > ? sendbackup: index tee cannot write [Broken pipe]
> 
> Note the problem was in making the index, not the backup.

But this is not relazed to a gzip. The gzip for the index always runs
on the server.

Instead this sound like /tmp full, probably on the client.

> > | DUMP: Broken pipe
> > | DUMP: The ENTIRE dump is aborted.
> > ? index returned 1
> > ??error [/sbin/dump returned 3, compress got signal 11]? dumper: strange 
> > [missing size line from sendbackup]
> > ? dumper: strange [missing end line from sendbackup]
> > \--------

And this is a result of the failed gzip; as already mentioned.

        Sven