samba - May 2002 - What's Happening

Found these messages in /var/log/dmesg on a Redhat 7.1 machine running
Samba 2.2.2 accessing a Win 2000 share.  Actually, there are a bunch of
tasks accessing the same share, complete with file locking, etc.

Any docs on what that error code means?

...Thanks,
...Kenneth


smb_get_length: recv error = 113
smb_trans2_request: result=-113, setting invalid
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_lookup: find syndex/.csafe.log.swp failed, error=-5
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/csafe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
smb_file_write: syndex/rcffe.log validation failed, error=4294967291
spurious 8259A interrupt: IRQ15.
smb_retry: successful, new pid=969, generation=2
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=969, generation=3
and this on athene
 
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=785, generation=2
smb_open: syndex/rcffe2.log open failed, result=-26
smb_open: syndex/rcffe2.log open failed, result=-26
smb_readpage_sync: syndex/rcffe2.log open failed, error=-26

On Fri, 24 May 2002, Kenneth Loafman wrote:
> Found these messages in /var/log/dmesg on a Redhat 7.1 machine running
> Samba 2.2.2 accessing a Win 2000 share.  Actually, there are a bunch of
> tasks accessing the same share, complete with file locking, etc.
smbfs does not support file locking to the remote side. The local
processes will lock between themselves but not vs anyone on the server
side.

> smb_get_length: recv error = 113
> smb_trans2_request: result=-113, setting invalid
113 is "No route to host" (/usr/include/asm/errno.h)

This error leads to smbfs dropping the connection it had.
> smb_file_write: syndex/csafe.log validation failed, error=4294967291
These errors look like random bits. There is no smbfs error code
4294967291. It can't validate that the file still exists because it no
longer has any connection and the new connection is not up yet.
> smb_file_write: syndex/csafe.log validation failed, error=4294967291
> smb_file_write: syndex/csafe.log validation failed, error=4294967291
> smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
> smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
> smb_file_write: syndex/cdrsfe.log validation failed, error=4294967291
> smb_lookup: find syndex/.csafe.log.swp failed, error=-5
-5 is -EIO. Same cause.
> smb_file_write: syndex/rcffe.log validation failed, error=4294967291
> spurious 8259A interrupt: IRQ15.
> smb_retry: successful, new pid=969, generation=2
And then it reconnects to the server.
> smb_trans2_request: result=-104, setting invalid
> smb_retry: successful, new pid=969, generation=3
104 is "Connection reset by peer". Since you don't have any times
on these
it's hard to say but it probably has nothing to do with the above. It
seems to be normal for a smb server to just disconnect clients when it
feels like it.

> and this on athene
>  
> smb_trans2_request: result=-104, setting invalid
> smb_retry: successful, new pid=785, generation=2
> smb_open: syndex/rcffe2.log open failed, result=-26
> smb_open: syndex/rcffe2.log open failed, result=-26
> smb_readpage_sync: syndex/rcffe2.log open failed, error=-26
-26 = -ETXTBSY

smbfs usually fails to open files that others have opened.

/Urban