From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z Date: Tue, 25 Mar 2008 15:09:43 -0400 Message-ID: <20080325190943.GF2237@fieldses.org> References: <47CF157B.1010908@m2000.com> <18383.24847.381754.517731@notabene.brown> <47CF62C5.7000908@m2000.com> <18384.50909.866848.966192@notabene.brown> <9a8748490803121513w285cd45rb6b26a3d842cac1b@mail.gmail.com> <20080312221511.GC31632@fieldses.org> <9a8748490803121516u36395872i70cc88b0439adc74@mail.gmail.com> <18394.1501.991087.80264@notabene.brown> <47DAEFD0.9020407@m2000.com> <47E92F8E.7030504@m2000.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Neil Brown , Jesper Juhl , Trond Myklebust , lkml@vger.kernel.org, linux-nfs@vger.kernel.org, Thomas Daniel , Frederic Revenu , Jeff Doan To: Adam Schrotenboer Return-path: Received: from mail.fieldses.org ([66.93.2.214]:33549 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755128AbYCYTJt (ORCPT ); Tue, 25 Mar 2008 15:09:49 -0400 In-Reply-To: <47E92F8E.7030504-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Mar 25, 2008 at 09:59:58AM -0700, Adam Schrotenboer wrote: > Adam Schrotenboer wrote: >> Neil Brown wrote: >>> On Wednesday March 12, jesper.juhl@gmail.com wrote: >>>> On 12/03/2008, J. Bruce Fields wrote: >>>>> What was the exported filesystem? >>>> XFS >>> >>> It's a bit of a long shot, but could you try mounting the XFS file >>> system with >>> -o ikeep >>> >>> and see if it makes a difference. >>> >>> When you have "ikeep", I can find the code that increments the >>> generation number between different uses of the one inode number. >>> >>> When you have "noikeep" (which I think is the default) it doesn't keep >>> the inode of disk when deleted and so (presumably) needs generate a >>> random generation number for each use. But I cannot find the code >>> that does that. I'm probably not looking in the right place, but I >>> don't think it can hurt to try "-o ikeep". >>> >>> NeilBrown >>> >> Ok, I've unmounted and remounted with that option enabled >> (/proc/mounts confirms it's enabled). We'll see what happens. > > Well, it's been almost 2 weeks (11 days anyhow) and I am not seeing > the nfs_update_inode message in the syslogs of any of our compute > servers. I need to talk to the various people who work with them to > verify, but it looks like this problem has been resolved. That's a workaround, at least, but it's unfortunate if a special mount option is required to get correct behavior for nfs exports. Is there anything we can do? --b.