Folks, I have a strange problem with smb connections from a Linux box to another Linux box. The clients syslog shows the following entries: Jun 17 02:33:27 client01 kernel: smb_proc_readdir_long: error=-512, breaking Jun 17 03:49:44 client01 kernel: smb_proc_readdir_long: error=-512, breaking Jun 17 04:50:13 client01 kernel: smb_proc_readdir_long: error=-512, breaking Jun 17 06:52:14 client01 kernel: smb_lookup: find some-file failed, error=-512 Jun 17 06:52:16 client01 kernel: smb_lookup: find otherfile failed, error=-512 Jun 17 06:52:18 client01 kernel: smb_lookup: find foo-file failed, error=-512 Jun 17 06:52:28 client01 kernel: smb_create: bar-file failed, error=-512 Jun 17 08:16:10 client01 kernel: smb_proc_readdir_long: error=-512, breaking Jun 17 08:16:26 client01 kernel: smb_lookup: find whatever-file failed, error=-512 Jun 17 08:16:45 client01 kernel: smb_create: yet-antother-file failed, error=-512 Jun 17 09:27:17 client01 kernel: smb_proc_readdir_long: error=-512, breaking Jun 17 09:47:45 client01 kernel: smb_create: you-name-it-file failed, error=-512 Finally there are comming errors like "Text file busy" and only the smbd is shown by lsof. Both, the server and the client are SuSE 9.1 with kernel 2.6.4-54.5 Also the samba versions are the same. To exclude that the errors are comming from a shaky network, I tried the same configuration on a testsystem, where the client connects via loopback to the same server. That system is running SuSE 9.1 with vanilla kernel 2.6.7-rc3 I'm not sure if I should post this to the linux-net or samba mailinglist. Since Windows clients to that machines seems not to have problems with the connection I think the error commes from somewhere in the kernelspace smb driver. Thanks for any hint. rgds Luc - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
