public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Schrotenboer <adam@m2000.com>
To: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Cc: Thomas Daniel <tdaniel@m2000.com>,
	jesper.juhl@gmail.com, Trond.Myklebust@netapp.com,
	Neil Brown <neilb@suse.de>
Subject: nfs_update_inode: inode X mode changed, Y to Z [repost with correct address]
Date: Wed, 05 Mar 2008 13:23:23 -0800	[thread overview]
Message-ID: <47CF0F4B.60801@m2000.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1125 bytes --]

      Running SLES 10 on multiple compute nodes, with an OpenSuSE 10.2 NFS
server, and I am receiving the above log message on a semi-regular basis
in the NFS client system-logs. When this occurs, one of the users
receives an error (although there seems to be no way to easily collate
the users experience with the system log, short of using the timestamp).
      Sometimes it's "read/write error", sometimes it's more specific
about something that was a file now being a directory (SVN tends to be
rather more verbose). Most of the time this is just a nuisance, but at
times (such as last week or so) it occurs so often that it blocks any
work getting done.

      The NFS Server is running OpenSuSE 10.2 on a Dell PowerEdge 2900
with the PERC5/i controller. The NFS Clients are all SLES10 with the
standard mountoptions, and running in TCP mode (something about UDP +
NFS + GbE leads to subtle data corruption).

      I have been able to find some references to this problem in Google,
but no solutions, and no discussion about what the problem stems from,
nor if any fixes have been attempted.





[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

                 reply	other threads:[~2008-03-05 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47CF0F4B.60801@m2000.com \
    --to=adam@m2000.com \
    --cc=Trond.Myklebust@netapp.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