From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 79F1D7F62 for ; Sun, 8 Mar 2015 10:31:05 -0500 (CDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay3.corp.sgi.com (Postfix) with ESMTP id 122F6AC001 for ; Sun, 8 Mar 2015 08:31:01 -0700 (PDT) Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) by cuda.sgi.com with ESMTP id 7LOrGs4dTYcfH7tp for ; Sun, 08 Mar 2015 08:31:00 -0700 (PDT) Date: Sun, 8 Mar 2015 16:30:56 +0100 From: Christoph Hellwig Subject: Re: panic on 4.20 server exporting xfs filesystem Message-ID: <20150308153056.GA24037@lst.de> References: <20150304220900.GX18360@dastard> <20150304222709.GI1627@fieldses.org> <20150304224557.GY4251@dastard> <54F78BE5.1020608@sandeen.net> <20150304225623.GZ4251@dastard> <20150305040849.GJ1627@fieldses.org> <20150305131731.GA16235@lst.de> <20150305150138.GA15674@fieldses.org> <20150305170217.GC15674@fieldses.org> <20150305204749.GA17934@fieldses.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20150305204749.GA17934@fieldses.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: "J. Bruce Fields" Cc: Eric Sandeen , linux-nfs@vger.kernel.org, Christoph Hellwig , xfs@oss.sgi.com On Thu, Mar 05, 2015 at 03:47:49PM -0500, J. Bruce Fields wrote: > nfsd: client 192.168.122.32 failed to respond to layout recall. Fencing.. > nfsd: fence failed for client 192.168.122.32: -2! > nfsd: client 192.168.122.32 failed to respond to layout recall. Fencing.. > nfsd: fence failed for client 192.168.122.32: -2! There is no userspace elper to do the fencing, so unfortunately this is expecvted. > receive_cb_reply: Got unrecognized reply: calldir 0x1 xpt_bc_xprt ffff88005639a000 xid c21abd62 Now this looks like some issue with the low-level callback path. I've never seen tis before, but from looking at receive_cb_reply this happens if xprt_lookup_rqst can't find a rpc_rqst structured for the xid. Looks like we might be corrupting the request list / xid allocation somewhere? I can prepare a patch for you to aid with xid tracing if you want. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs