Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753446AbZIIRI5 (ORCPT ); Wed, 9 Sep 2009 13:08:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753157AbZIIRI4 (ORCPT ); Wed, 9 Sep 2009 13:08:56 -0400 Received: from smtp2.ultrahosting.com ([74.213.174.253]:54766 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752908AbZIIRIz (ORCPT ); Wed, 9 Sep 2009 13:08:55 -0400 Date: Wed, 9 Sep 2009 13:07:52 -0400 (EDT) From: Christoph Lameter X-X-Sender: cl@V090114053VZO-1 To: Jeff Layton cc: linux-kernel@vger.kernel.org, samba@lists.samba.org, linux-cifs-client@lists.samba.org Subject: Re: 2.6.31-rc8: CIFS with 5 seconds hiccups In-Reply-To: <20090909125352.1c7b57d2@tlielax.poochiereds.net> Message-ID: References: <20090905071052.50501826@tlielax.poochiereds.net> <20090909125352.1c7b57d2@tlielax.poochiereds.net> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 760 Lines: 20 On Wed, 9 Sep 2009, Jeff Layton wrote: > My suspicion would be that the server needs to perform an oplock break > to another client before it can send the response. The only way I know > how to tell that is to sniff all SMB traffic on the server and watch > for oplock break calls to other clients when these stalls occur. That could be tested by switching them off right? If I do echo 0 >/proc/fs/cifs/OplockEnabled and then remount the volume it should switch off oplocks? This has no effect on the stalls. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/