linux-kernel - nfs_update_inode: inode X mode changed, Y to Z [repost with correct address]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <47CF0F4B.60801@m2000.com>
Date:	Wed, 05 Mar 2008 13:23:23 -0800
From:	Adam Schrotenboer <adam@...00.com>
To:	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org
Cc:	Thomas Daniel <tdaniel@...00.com>, jesper.juhl@...il.com,
	Trond.Myklebust@...app.com, Neil Brown <neilb@...e.de>
Subject: nfs_update_inode: inode X mode changed, Y to Z [repost with correct
 address]

      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.





Download attachment "signature.asc" of type "application/pgp-signature" (260 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)