From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Holger Hoffstaette" <holger@wizards.de>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
stable@kernel.org
Subject: Re: Nasty regression from .27.7 to .27.8: idle samba goes crazy
Date: Mon, 8 Dec 2008 08:34:22 +0100 [thread overview]
Message-ID: <200812080834.22924.rjw@sisk.pl> (raw)
In-Reply-To: <pan.2008.12.08.06.18.57.357875@wizards.de>
On Monday, 8 of December 2008, Holger Hoffstaette wrote:
>
> Hi,
>
> I just encountered a nasty symptom for the second time that has started to
> occur after updating my home server from vanilla 2.6.27.7 to .8 (same
> config).
>
> A while after disconnecting a samba client, the smbd samba server
> process goes crazy and consumes 100% CPU. From that time on it is
> unkillable (kill -9 returns but the process continues to run). The only
> recourse is reboot, which works without problem (i.e. unmounting the
> served filesystems is apparently possible?). I tried to attach to the
> process with gdb but that just hung.
>
> The system is a generic old single-core P4 box with a single SATA drive,
> Gentoo userland and Samba is 3.0.33 (in async mode). The kernel has no
> patches or binary drivers. It has been rock solid before the update and
> shows no other signs of weirdness in logs or otherwise. I downgraded to .7
> for now and will see what happens, but since it worked before I am certain
> that this is a regression in the .8 release.
>
> The only commonality is a log entry by samba that seems to correlate with
> both occurrences:
>
> [2008/12/08 01:02:52, 0] lib/util_sock.c:read_data(534)
> read_data: read failure for 4 bytes to client 192.168.100.128. Error = No route to host
>
> .128 is the Windows client machine (connected via a stable GigE link),
> which I shut down pretty much exactly 30 minutes before that (any 30
> minute timeouts in the kernel/network stack?). Both instances of these log
> entries correlate with the CPU spikes which I noticed in my MRTG graphs.
>
> Any suspects or ideas?
Please bisect.
Thanks,
Rafael
next prev parent reply other threads:[~2008-12-08 7:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 6:18 Nasty regression from .27.7 to .27.8: idle samba goes crazy Holger Hoffstaette
2008-12-08 7:34 ` Rafael J. Wysocki [this message]
2008-12-08 8:07 ` Holger Hoffstaette
2008-12-08 16:46 ` Stefan Richter
2008-12-08 19:19 ` Stefan Richter
2008-12-08 20:08 ` Holger Hoffstaette
2008-12-08 22:22 ` Jan Rekorajski
2008-12-09 17:37 ` Chuck Ebbert
2008-12-09 19:16 ` Manfred Spraul
2008-12-09 19:30 ` Chuck Ebbert
2008-12-10 17:37 ` Manfred Spraul
2008-12-11 22:54 ` Holger Hoffstätte
2008-12-11 23:40 ` [stable] " Greg KH
2008-12-12 10:59 ` Holger Hoffstätte
2008-12-12 1:08 ` Jan Rekorajski
2008-12-12 18:26 ` Jan Rekorajski
2008-12-12 14:01 ` Holger Hoffstätte
2008-12-08 16:32 ` Stefan Richter
2008-12-08 18:46 ` Rafael J. Wysocki
2008-12-08 19:14 ` Stefan Richter
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=200812080834.22924.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=greg@kroah.com \
--cc=holger@wizards.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.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