From: Adam Schrotenboer <adam-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Thomas Daniel <tdaniel-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>,
jesper.juhl@gmail.com,
Fred Revenu <frevenu-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z
Date: Wed, 12 Mar 2008 11:16:04 -0700 [thread overview]
Message-ID: <47D81DE4.5040303@m2000.com> (raw)
In-Reply-To: <1205345284.9419.8.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Trond Myklebust wrote:
> 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?
>
>
Quite. OpenSuSE 10.2 stock unmodified kernel.
dolphin:~ # uname -a
Linux dolphin 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006
x86_64 x86_64 x86_64 GNU/Linux
dolphin:~ # top -bn1 |grep nfsd
PID PPID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3916 1 root 15 0 0 0 0 S 0 0.0 3:04.42 nfsd
3942 1 root 15 0 0 0 0 S 0 0.0 3:11.88 nfsd
(there's quite a bit more of these threads than this (32), but they all
look the same in top or ps)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Adam Schrotenboer <adam@m2000.com>
To: Trond Myklebust <Trond.Myklebust@netapp.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 11:16:04 -0700 [thread overview]
Message-ID: <47D81DE4.5040303@m2000.com> (raw)
In-Reply-To: <1205345284.9419.8.camel@heimdal.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Trond Myklebust wrote:
> 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?
>
>
Quite. OpenSuSE 10.2 stock unmodified kernel.
dolphin:~ # uname -a
Linux dolphin 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006
x86_64 x86_64 x86_64 GNU/Linux
dolphin:~ # top -bn1 |grep nfsd
PID PPID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3916 1 root 15 0 0 0 0 S 0 0.0 3:04.42 nfsd
3942 1 root 15 0 0 0 0 S 0 0.0 3:11.88 nfsd
(there's quite a bit more of these threads than this (32), but they all
look the same in top or ps)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2008-03-12 18:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 20:52 [opensuse] nfs_update_inode: inode X mode changed, Y to Z Adam Schrotenboer
[not found] ` <47CF0829.4020502-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
2008-03-05 21:27 ` Trond Myklebust
[not found] ` <1204752463.5035.34.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-03-05 21:49 ` Adam Schrotenboer
2008-03-06 3:12 ` Neil Brown
[not found] ` <18383.24847.381754.517731-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-03-06 3:19 ` Adam Schrotenboer
2008-03-07 4:38 ` Neil Brown
[not found] ` <18384.50909.866848.966192-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-03-07 5:55 ` Adam Schrotenboer
2008-03-07 5:55 ` Adam Schrotenboer
[not found] ` <47D0D8B5.6050403-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
2008-03-12 17:55 ` Adam Schrotenboer
2008-03-12 17:55 ` Adam Schrotenboer
[not found] ` <47D818FB.8080302-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
2008-03-12 18:08 ` Trond Myklebust
2008-03-12 18:08 ` Trond Myklebust
[not found] ` <1205345284.9419.8.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-03-12 18:16 ` Adam Schrotenboer [this message]
2008-03-12 18:16 ` Adam Schrotenboer
2008-03-12 22:13 ` Jesper Juhl
[not found] ` <9a8748490803121513w285cd45rb6b26a3d842cac1b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-12 22:15 ` J. Bruce Fields
2008-03-12 22:16 ` Jesper Juhl
2008-03-14 4:58 ` Neil Brown
[not found] ` <18394.1501.991087.80264-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-03-14 21:21 ` Jesper Juhl
2008-03-14 21:36 ` Adam Schrotenboer
[not found] ` <47DAEFD0.9020407-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
2008-03-25 16:59 ` Adam Schrotenboer
[not found] ` <47E92F8E.7030504-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
2008-03-25 19:09 ` J. Bruce Fields
2008-03-25 20:32 ` NeilBrown
2008-03-25 20:32 ` NeilBrown
[not found] ` <32953.192.168.1.70.1206477121.squirrel-eq65iwfR9nKIECXXMXunQA@public.gmane.org>
2008-03-25 21:24 ` Josef 'Jeff' Sipek
2008-03-25 21:24 ` Josef 'Jeff' Sipek
[not found] ` <20080325212425.GA20257-PM1Ls4bqFqUFEYicpp4bmg@public.gmane.org>
2008-03-25 21:38 ` NeilBrown
2008-03-25 21:38 ` NeilBrown
[not found] ` <34178.192.168.1.70.1206481102.squirrel-eq65iwfR9nKIECXXMXunQA@public.gmane.org>
2008-03-25 22:13 ` Josef 'Jeff' Sipek
2008-03-25 22:13 ` Josef 'Jeff' Sipek
[not found] ` <20080325221321.GC20257-PM1Ls4bqFqUFEYicpp4bmg@public.gmane.org>
2008-03-25 23:09 ` NeilBrown
2008-03-25 23:09 ` NeilBrown
2008-03-26 3:37 ` David Chinner
2008-03-26 3:37 ` David Chinner
2008-03-26 5:02 ` David Chinner
2008-03-26 5:02 ` David Chinner
2008-04-17 19:37 ` Adam Schrotenboer
2008-03-26 3:27 ` Timothy Shimmin
2008-03-26 3:27 ` Timothy Shimmin
[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
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=47D81DE4.5040303@m2000.com \
--to=adam-pmr2dcmmwyeavxtiumwx3w@public.gmane.org \
--cc=Trond.Myklebust@netapp.com \
--cc=frevenu-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tdaniel-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.