From: Adam Schrotenboer <adam-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>
To: Stephan Jansen <jansen-IwvncFSHKSLQAyQhgwMYSA@public.gmane.org>
Cc: opensuse@opensuse.org,
Thomas Daniel <tdaniel-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
jesper.juhl@gmail.com,
Fred Revenu <frevenu-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org>,
Neil Brown <neilb@suse.de>
Subject: Re: nfs_update_inode: inode X mode changed, Y to Z
Date: Wed, 12 Mar 2008 11:06:02 -0700 [thread overview]
Message-ID: <47D81B8A.7040702@m2000.com> (raw)
In-Reply-To: <3AD71C5E-B45A-4BDB-8C94-73D62256BEBF-IwvncFSHKSLQAyQhgwMYSA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]
Stephan Jansen wrote:
>
> Hi,
>
> We've just run into a similar thing. We have an OpenSuSE 10.3 NFS server
> exporting a filesystem to about 40 machines, most of which are also
> running OpenSuSE 10.3. The client machines are running a distributed
> data processing pipeline. The clients create, move and delete
> directories
> and files on the server. We've seen a few instances where the
> programs on
> the clients die with a "no such file or directory" error but no errors in
> syslog. Finally last night many of the clients gave these errors in
> syslog
> at about the same time as the client programs died with "no such file or
> directory" errors:
>
> Mar 11 20:57:53 glimpse5 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:57:54 glimpse6 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:57:49 tsingtao kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:57:16 glimpse12 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:04 cecilia kernel: nfs_update_inode: inode 402653248 mode
> changed, 0100644 to 0040755
> Mar 11 20:59:11 glimpse28 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:58:20 glimpse27 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:12 glimpse18 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:58:22 glimpse19 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:25 glimpse20 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:58:35 glimpse21 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:27 glimpse22 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:27 glimpse23 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:39 glimpse24 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
>
> I notice that the offending inodes are all the same. This all worked
> without
> problems when the NFS server was SuSE 10.0. The exported filesystem
> is XFS.
>
> Anyone have any ideas what's going on?
I personally don't, but I have a running thread with some of the NFS
maintainers, that I have added this mail to now.
[-- 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: Stephan Jansen <jansen@astro.wisc.edu>
Cc: opensuse@opensuse.org, Thomas Daniel <tdaniel@m2000.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
jesper.juhl@gmail.com, Fred Revenu <frevenu@m2000.com>,
Neil Brown <neilb@suse.de>
Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z
Date: Wed, 12 Mar 2008 11:06:02 -0700 [thread overview]
Message-ID: <47D81B8A.7040702@m2000.com> (raw)
In-Reply-To: <3AD71C5E-B45A-4BDB-8C94-73D62256BEBF@astro.wisc.edu>
[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]
Stephan Jansen wrote:
>
> Hi,
>
> We've just run into a similar thing. We have an OpenSuSE 10.3 NFS server
> exporting a filesystem to about 40 machines, most of which are also
> running OpenSuSE 10.3. The client machines are running a distributed
> data processing pipeline. The clients create, move and delete
> directories
> and files on the server. We've seen a few instances where the
> programs on
> the clients die with a "no such file or directory" error but no errors in
> syslog. Finally last night many of the clients gave these errors in
> syslog
> at about the same time as the client programs died with "no such file or
> directory" errors:
>
> Mar 11 20:57:53 glimpse5 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:57:54 glimpse6 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:57:49 tsingtao kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:57:16 glimpse12 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:04 cecilia kernel: nfs_update_inode: inode 402653248 mode
> changed, 0100644 to 0040755
> Mar 11 20:59:11 glimpse28 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:58:20 glimpse27 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:12 glimpse18 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:58:22 glimpse19 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:25 glimpse20 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:58:35 glimpse21 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:27 glimpse22 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:27 glimpse23 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
> Mar 11 20:59:39 glimpse24 kernel: nfs_update_inode: inode 402653248
> mode changed, 0100644 to 0040755
>
> I notice that the offending inodes are all the same. This all worked
> without
> problems when the NFS server was SuSE 10.0. The exported filesystem
> is XFS.
>
> Anyone have any ideas what's going on?
I personally don't, but I have a running thread with some of the NFS
maintainers, that I have added this mail to now.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next parent reply other threads:[~2008-03-12 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47C5EC81.6080004@m2000.com>
[not found] ` <47C71EC6.3050702@m2000.com>
[not found] ` <3AD71C5E-B45A-4BDB-8C94-73D62256BEBF@astro.wisc.edu>
[not found] ` <3AD71C5E-B45A-4BDB-8C94-73D62256BEBF-IwvncFSHKSLQAyQhgwMYSA@public.gmane.org>
2008-03-12 18:06 ` Adam Schrotenboer [this message]
2008-03-12 18:06 ` [opensuse] nfs_update_inode: inode X mode changed, Y to Z Adam Schrotenboer
2007-02-23 22:32 Yaroslav Halchenko
2007-03-20 20:52 ` Yaroslav Halchenko
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=47D81B8A.7040702@m2000.com \
--to=adam-pmr2dcmmwyeavxtiumwx3w@public.gmane.org \
--cc=Trond.Myklebust@netapp.com \
--cc=frevenu-PMR2DCmmWYEAvxtiuMwx3w@public.gmane.org \
--cc=jansen-IwvncFSHKSLQAyQhgwMYSA@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=opensuse@opensuse.org \
--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.