Ok, after some more testing with a variety of tar's I've got compiled
around I traced it back to the version of tar that was being used was
indeed 1.13.25, but it had been compiled with gcc 2.8.1!

Recompiled with gcc-2.95.2 and everything works as desired.

Thanks to everyone who responded,
Murf


> --- Murf <jam AT philabs.research.philips DOT com> wrote:
> We're using amanda and GNU tar (1.13.25) to backup a
> new Netapp to a Solaris 8 Sun.
>
> The first pilot users moved to the Netapp went fine, and then amanda
> started acting up.  The symptom was tar was grinding on one of the CPUs
>
> ...
> .  What I've traced it back to, is one of
> the users I migrated to the Netapp had a very long file name in his .kde
> http cache
>
> Obviously nothing he tried to create.  Now the pathname is 131 chars long,
> and the basename of the file is 101 chars.  By renaming the file tar went
> along happily.
>
> ...
> Has anyone else seen similar behavior?

-- 
John Murphy, better known as Erin's & Kevin's dad    http://remarque.org/~jam
John.Murphy AT philips DOT com       One one-trillionith of a surprise: picoboo
345 Scarborough Road          millihellen: The beauty needed to launch 1 ship
Briarcliff Manor, NY 10510 ** My opinions do not reflect those of my employer **