Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755224AbYCLSIZ (ORCPT ); Wed, 12 Mar 2008 14:08:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754359AbYCLSII (ORCPT ); Wed, 12 Mar 2008 14:08:08 -0400 Received: from mx2.netapp.com ([216.240.18.37]:35403 "EHLO mx2.netapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754145AbYCLSIG (ORCPT ); Wed, 12 Mar 2008 14:08:06 -0400 X-IronPort-AV: E=Sophos;i="4.25,489,1199692800"; d="scan'208";a="8685525" Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z From: Trond Myklebust To: Adam Schrotenboer Cc: Neil Brown , linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org, Thomas Daniel , jesper.juhl@gmail.com, Fred Revenu In-Reply-To: <47D818FB.8080302@m2000.com> References: <47CF0829.4020502@m2000.com> <1204752463.5035.34.camel@heimdal.trondhjem.org> <47CF157B.1010908@m2000.com> <18383.24847.381754.517731@notabene.brown> <47CF62C5.7000908@m2000.com> <18384.50909.866848.966192@notabene.brown> <47D0D8B5.6050403@m2000.com> <47D818FB.8080302@m2000.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Network Appliance Inc Date: Wed, 12 Mar 2008 14:08:03 -0400 Message-Id: <1205345284.9419.8.camel@heimdal.trondhjem.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 X-OriginalArrivalTime: 12 Mar 2008 18:08:04.0839 (UTC) FILETIME=[0496DF70:01C8846C] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1253 Lines: 35 On Wed, 2008-03-12 at 10:55 -0700, Adam Schrotenboer wrote: > Another excerpt from last night. > > Mar 12 00:53:16 wanda kernel: nfs: server 192.168.1.27 not responding, > still trying > Mar 12 00:53:18 wanda kernel: nfs: server 192.168.1.27 OK > Mar 12 00:54:29 wanda kernel: nfs_update_inode: inode 1075049148 mode > changed, 0040755 to 0100644 Hang on. That does not look like an XID collision problem... That code path basically means that the fileids/inode numbers match, which would not be the case if we were talking about an XID collision causing the reply cache to replay an old request... That message rather symptomatic of a filehandle reuse problem. In other words a NFS filehandle appears to be reused to label a regular file after it has been used for a directory with the same fileid/inode number. That is a definite server bug. Are you sure that you are using the regular kernel nfs server? -- Trond Myklebust NFS client maintainer NetApp Trond.Myklebust@netapp.com www.netapp.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/