mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 --]

       reply	other threads:[~2008-03-12 18:06 UTC|newest]

Thread overview: 10+ 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>
2008-03-12 18:06     ` Adam Schrotenboer [this message]
     [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
     [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
2008-03-12 18:16                 ` 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=47D81B8A.7040702@m2000.com \
    --to=adam@m2000.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=frevenu@m2000.com \
    --cc=jansen@astro.wisc.edu \
    --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@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

Powered by JetHome