On Mon, Aug 17, 2009 at 4:32 PM, stan<stanb AT panix DOT com> wrote:
> On Tue, Aug 18, 2009 at 09:32:21AM -0400, Jean-Louis Martineau wrote:
>> From the write man page:
>>
>>     [EAGAIN]       The file was marked for non-blocking I/O, and no data
>>     could
>>                    be written immediately.
>>
>>
>> But sendbackup or gzip write the index to a blocking pipe.
>> Maybe it's the firewall that returns that error.
>>
>> You can try to switch to the 'bsdtcp' auth, it is a lot more firewall
>> friendly.
>>
> Same result:
>
> 1250605398.423331: sendbackup:  91:  normal(|):   DUMP: Volume 1 started at: 
> Tue
>  Aug 18 10:23:18 2009
> 1250605398.435367: sendbackup: critical (fatal): index tee cannot write 
> [Resourc e temporarily unavailable]
> 1250605398.437948: sendbackup: 116: strange(?): sendbackup: index tee cannot 
> write [Resource temporarily unavailable]
> 1250605398.439291: sendbackup:  91:  normal(|):   DUMP: Broken pipe
> 1250605398.440143: sendbackup:  91:  normal(|):   DUMP: The ENTIRE dump is 
> aborted.
> 1250605398.440752: sendbackup: critical (fatal): error [dump (7497) 
> /sbin/dump r
>  eturned 3]
>
>  I know I have asked this before, but I can't recall getting a definative
>  answer. Is port usage different between 2.5.x and 2.6 clients, when
>  talkimng to a 2.6 server?

i have no idea what else your system is doing. is it possible you're
simply running out of file descriptors?
pstat -T | grep open