On Tue, 20 Nov 2007 13:57:39 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:

> Hi Andrew,
> 
> Following calltrace is seen server, while running filesystem stress on smb 
> mounted partition on the client machine.
> 
> Nov 19 18:45:52 p55lp6 smbd[3304]: [2007/11/19 18:45:52, 0] 
> lib/util_sock.c:write_data(562)
> Nov 19 18:45:52 p55lp6 smbd[3304]:   write_data: write failure in writing to 
> client 9.124.111.212. Error Broken pipe
> Nov 19 18:45:52 p55lp6 smbd[3304]: [2007/11/19 18:45:52, 0] 
> lib/util_sock.c:send_smb(769)
> Nov 19 18:45:52 p55lp6 smbd[3304]:   Error writing 39 bytes to client. -1. 
> (Broken pipe)
> Nov 19 18:47:42 p55lp6 smbd[3650]: [2007/11/19 18:47:42, 0] 
> smbd/oplock.c:oplock_timeout_handler(351)
> Nov 19 18:47:42 p55lp6 smbd[3650]:   Oplock break failed for file 
> p0/d3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/deX/d3cX/d6eXXX/f8d -- replying 
> anyway
> Nov 19 18:47:42 p55lp6 kernel: [ 6960.261068] warning: process `smbd' gets w/ 
> old libcap
> Nov 19 18:47:42 p55lp6 smbd[3650]: [2007/11/19 18:47:42, 0] 
> smbd/oplock_linux.c:linux_release_kernel_oplock(193)
> Nov 19 18:47:43 p55lp6 smbd[3650]:   linux_release_kernel_oplock: Error when 
> removing kernel oplock on file p0/d3XXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/deX/d3cX/d6eXXX/f8d,
>  dev = 807, inode = 30983, file
> _id = 501. Error w
> Nov 19 18:48:04 p55lp6 smbd[3650]: [2007/11/19 18:48:04, 0] 
> lib/util_sock.c:write_data(562)
> Nov 19 18:48:04 p55lp6 smbd[3650]:   write_data: write failure in writing to 
> client 9.124.111.212. Error Connection reset by peer
> 

So you have samba running on a 2.6.24-rc2-mm1 machine and samba is failing
with the above messages?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to