Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753109Ab0KASTm (ORCPT ); Mon, 1 Nov 2010 14:19:42 -0400 Received: from dsl-67-204-24-19.acanac.net ([67.204.24.19]:57702 "EHLO mail.ellipticsemi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751817Ab0KASTk (ORCPT ); Mon, 1 Nov 2010 14:19:40 -0400 Date: Mon, 1 Nov 2010 14:19:38 -0400 From: Nick Bowler To: Chuck Lever Cc: LKML Kernel , "J. Bruce Fields" , Linux NFS Mailing List Subject: Re: Regression, bisected: sqlite locking failure on nfs Message-ID: <20101101181938.GA3875@elliptictech.com> Mail-Followup-To: Chuck Lever , LKML Kernel , "J. Bruce Fields" , Linux NFS Mailing List References: <20101101175854.GA3550@elliptictech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Elliptic Technologies Inc. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1834 Lines: 44 On 2010-11-01 14:07 -0400, Chuck Lever wrote: > On Nov 1, 2010, at 1:58 PM, Nick Bowler wrote: > > After installing 2.6.37-rc1, attempting to use sqlite in any capacity on > > NFS gives a locking error: > > > > % echo 'select * from blah;' | sqlite3 blah.sqlite > > Error: near line 1: database is locked > > > > % echo 'create table blargh(INT);' | sqlite3 blargh.sqlite > > Error: near line 1: database is locked > > > > The result is that a lot of high-profile applications which make use of > > sqlite fail mysteriously. Bisection reveals the following, and > > reverting the implicated commit solves the issue: > > Nick, thanks for the report. Is 2.6.37-rc1 running on your clients or > on your server? Sorry for not being clear: the client is running 2.6.37-rc1. The server is running RHEL 5.5. > Does anything interesting appear in the kernel log when your test case > fails? There are no unusual messages on the client... but I just logged into the server and I see lots of messages of the following form: nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! (192.168.8.199 is the address of the failing client). I can only assume that these are a result of my recent issues, since I don't have access to the system log (with timestamps) on that machine. -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/) -- 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/