Rodrigo Ventura <yoda AT isr.ist.utl DOT pt> writes:

> This just happened this night amdump:
>
> (/tmp/amanda/sendbackup.20051128003448.debug)
> [...]
> sendbackup: time 3.133: index created successfully
> sendbackup: time 3.134: error [/bin/tar got signal 11]
> sendbackup: time 3.134: pid 13222 finish time Mon Nov 28 00:34:51 2005
>
> Signal 11 is SIGSEGV. My tar is (GNU tar) 1.13.25.
>
> Has this ever happened to anyone here?

We run a job that syncs /etc/passwd from a remote source. Sometimes
this jobs is triggered continuously; and then /etc/passwd is written
many times per second. This causes tar to receive SIGSEGV.

In above situation I can reproduce the problem and I can strace
tar. AFAIR tar mmappes /etc/passwd and failes when it tries to read an
already-deleted mmapped /etc/passwd.

        Sven