From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Adam Schrotenboer <adam@m2000.com>
Cc: Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Thomas Daniel <tdaniel@m2000.com>,
jesper.juhl@gmail.com, Fred Revenu <frevenu@m2000.com>
Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z
Date: Wed, 12 Mar 2008 14:08:03 -0400 [thread overview]
Message-ID: <1205345284.9419.8.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <47D818FB.8080302@m2000.com>
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
next prev parent reply other threads:[~2008-03-12 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47CF0829.4020502@m2000.com>
[not found] ` <1204752463.5035.34.camel@heimdal.trondhjem.org>
[not found] ` <47CF157B.1010908@m2000.com>
[not found] ` <18383.24847.381754.517731@notabene.brown>
[not found] ` <47CF62C5.7000908@m2000.com>
[not found] ` <18384.50909.866848.966192@notabene.brown>
2008-03-07 5:55 ` Adam Schrotenboer
2008-03-12 17:55 ` Adam Schrotenboer
2008-03-12 18:08 ` Trond Myklebust [this message]
2008-03-12 18:16 ` Adam Schrotenboer
[not found] <47C5EC81.6080004@m2000.com>
[not found] ` <47C71EC6.3050702@m2000.com>
[not found] ` <3AD71C5E-B45A-4BDB-8C94-73D62256BEBF@astro.wisc.edu>
2008-03-12 18:06 ` Adam Schrotenboer
[not found] <9a8748490803121513w285cd45rb6b26a3d842cac1b@mail.gmail.com>
[not found] ` <20080312221511.GC31632@fieldses.org>
[not found] ` <9a8748490803121516u36395872i70cc88b0439adc74@mail.gmail.com>
[not found] ` <18394.1501.991087.80264@notabene.brown>
[not found] ` <47DAEFD0.9020407@m2000.com>
[not found] ` <47E92F8E.7030504@m2000.com>
[not found] ` <20080325190943.GF2237@fieldses.org>
[not found] ` <32953.192.168.1.70.1206477121.squirrel@neil.brown.name>
[not found] ` <20080325212425.GA20257@josefsipek.net>
[not found] ` <34178.192.168.1.70.1206481102.squirrel@neil.brown.name>
2008-03-25 22:13 ` Josef 'Jeff' Sipek
2008-03-25 23:09 ` NeilBrown
2008-03-26 3:37 ` David Chinner
2008-03-26 5:02 ` David Chinner
2008-04-17 19:37 ` Adam Schrotenboer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1205345284.9419.8.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=adam@m2000.com \
--cc=frevenu@m2000.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tdaniel@m2000.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®