From: Andrew Morton <akpm@linux-foundation.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-cifs-client@lists.samba.org,
samba-technical@lists.samba.org,
Andy Whitcroft <apw@shadowen.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [BUG] 2.6.24-rc2-mm1 - smbd write fails
Date: Tue, 20 Nov 2007 01:24:46 -0800 [thread overview]
Message-ID: <20071120012446.f97c5467.akpm@linux-foundation.org> (raw)
In-Reply-To: <4742A05B.40902@linux.vnet.ibm.com>
On Tue, 20 Nov 2007 14:22:43 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> Andrew Morton wrote:
> > On Tue, 20 Nov 2007 13:57:39 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> 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?
> >
> Hi Andrew,
>
> Yes, the above messages are seen with the 2.6.24-rc2-mm1 kernel.
Oh. Well I don't know where to start looking for that one.
Maybe someone fixed it amongst all the things which have been happening
recently. I'll upload an mm snapshot as soon as I can get some of it to
compile. Can you please retest with that?
If it still fails and if this is reasonably reproducible I'm afraid I'd ask
if you have time to run a bisection search on it.
next prev parent reply other threads:[~2007-11-20 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 8:27 [BUG] 2.6.24-rc2-mm1 - smbd write fails Kamalesh Babulal
2007-11-20 8:38 ` Andrew Morton
2007-11-20 8:52 ` Kamalesh Babulal
2007-11-20 9:24 ` Andrew Morton [this message]
2007-11-20 9:40 ` Kamalesh Babulal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071120012446.f97c5467.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox