Linux NFS development
 help / color / mirror / Atom feed
* Re: nfs_update_inode: inode X mode changed, Y to Z
       [not found]     ` <3AD71C5E-B45A-4BDB-8C94-73D62256BEBF-IwvncFSHKSLQAyQhgwMYSA@public.gmane.org>
@ 2008-03-12 18:06       ` Adam Schrotenboer
  0 siblings, 0 replies; only message in thread
From: Adam Schrotenboer @ 2008-03-12 18:06 UTC (permalink / raw)
  To: Stephan Jansen
  Cc: opensuse, Thomas Daniel, Trond Myklebust, linux-kernel, linux-nfs,
	jesper.juhl, Fred Revenu, Neil Brown

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-03-12 18:06 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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       ` nfs_update_inode: inode X mode changed, Y to Z Adam Schrotenboer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox