From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756614Ab1BCTl0 (ORCPT ); Thu, 3 Feb 2011 14:41:26 -0500 Received: from mail-gw0-f46.google.com ([74.125.83.46]:33891 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756491Ab1BCTlZ (ORCPT ); Thu, 3 Feb 2011 14:41:25 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=F/pYVA+ovr1asFU48uBYutz3UJcCL99T1XucpFuUztgD+R5xhMePFCMdVeoSjmKERo CTm9IBKL13qlUS6IUIO4W9aEls4DbhIz0HY1HHCi/HCPsGYdnFaYlO+p8tvkkt2RWLYr F2IhFKLwj8Wd1l/6gjKFS8S0O09C1GGaRWFqM= Date: Thu, 3 Feb 2011 11:41:15 -0800 From: Dmitry Torokhov To: Miklos Szeredi Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.38-rc3: FUSE (sshfs) hangs under load Message-ID: <20110203194115.GA14159@core.coreip.homeip.net> References: <20110201175452.GB518@core.coreip.homeip.net> <20110202165236.GA3178@core.coreip.homeip.net> <20110203065541.GB5592@core.coreip.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 03, 2011 at 12:13:24PM +0100, Miklos Szeredi wrote: > On Wed, 2 Feb 2011, Dmitry Torokhov wrote: > > --/9DWx/yDrRhgMJTb > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > > > On Wed, Feb 02, 2011 at 08:52:36AM -0800, Dmitry Torokhov wrote: > > > On Wed, Feb 02, 2011 at 12:52:36PM +0100, Miklos Szeredi wrote: > > > > On Tue, 1 Feb 2011, Dmitry Torokhov wrote: > > > > > Hi, > > > > > > > > > > After installing 2.6.38-rc3 (plus a few input patches) sshfs started to > > > > > misbehave on me under load. It starts off fine but when I try to compile > > > > > a few modules against kernel sources residing on the other box the > > > > > processes go into 'D' state and just sit there doing nothing. > > > > > > > > Can you please post a stack trace from SysRq-T? > > > > > > > > > > Will do tonight. In the meantime I tried bisecting, but failure is not > > > always triggered on the first attempt so results are iffy. The log so > > > far: > > > > > > # bad: [7d44b0440147d83a65270205b22e7d365de28948] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse > > > # good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37 > > > git bisect start '7d44b0440147d83a65270205b22e7d365de28948' 'v2.6.37' > > > # bad: [84b7290cca16c61a167c7e1912cd84a479852165] Merge git://git.kernel.org/pub/scm/linux/kernel/git/lethal/fbdev-2.6 > > > git bisect bad 84b7290cca16c61a167c7e1912cd84a479852165 > > > # good: [fea9294c5f2902c45613681ad995ca27899d2016] pch_can: Optimize "if" condition in rx/tx processing > > > git bisect good fea9294c5f2902c45613681ad995ca27899d2016 > > > # bad: [c96e96354a6c9456cdf1f150eca504e2ea35301e] Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6 into for-davem > > > git bisect bad c96e96354a6c9456cdf1f150eca504e2ea35301e > > > # good: [003ea98195eebdfcf476317b517e8c29a25b9d10] iwlwifi: remove reference to Gen2 > > > git bisect good 003ea98195eebdfcf476317b517e8c29a25b9d10 > > > > > > The last good must have been also bad as sshfs got stuck while I was > > > installing next bisect step over it. > > > > > > > OK, so here are the stack traces you requested. First one is snapshot of > > when compile got stuck, the 2nd one is when I interrupted make which > > caused gcc to go to 'D' state. > > There doesn't appear anything abnormal there. > > It's going into D state after it has received an interrupt and sent it > along to the userspace filesystem. Then it will go into > uninterruptible sleep until the answer is received. > > So the hang is because the answer to an open request is not being > received. I can't tell where it got stuck, apparently not anywhere on > the local machine. > > Can you please get a log from sshfs with "-odebug,sshfs_debug" and > redirect stderr to a file? That might tell a bit more about the > situation. Or it might not... Hmm, it might be just the network itself, last night mutt in ssh session froze on me as well. I guess I'll just have to finish my bisect exercise. Thanks. -- Dmitry