All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: nfs@lists.sourceforge.net
Cc: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: nfs_update_inode: inode 309229856 mode changed, 0100644 to 0040755 - kernel 2.6.13.4
Date: Mon, 26 Feb 2007 14:31:02 +0100	[thread overview]
Message-ID: <9a8748490702260531h45a91113o611c272c0fe7b39f@mail.gmail.com> (raw)

I have a webserver running a rather old 2.6.13.4 kernel that a few
minutes ago surprised me by logging the following message :

 kernel: nfs_update_inode: inode 309229856 mode changed, 0100644 to 0040755

The server exporting the filesystem is running 2.6.18.1 (knfsd) -
nothing is logged on the server...

So a file changed type and permissions out of the blue.  A few
questions about that:

Any way I can identify the file (or is it a dir now ;) ?
Does anyone know if this is a known bug that's been fixed? I couldn't
find anything via google or git that looked like a fix.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

WARNING: multiple messages have this Message-ID (diff)
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: nfs@lists.sourceforge.net
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: nfs_update_inode: inode 309229856 mode changed, 0100644 to 0040755 - kernel 2.6.13.4
Date: Mon, 26 Feb 2007 14:31:02 +0100	[thread overview]
Message-ID: <9a8748490702260531h45a91113o611c272c0fe7b39f@mail.gmail.com> (raw)

I have a webserver running a rather old 2.6.13.4 kernel that a few
minutes ago surprised me by logging the following message :

 kernel: nfs_update_inode: inode 309229856 mode changed, 0100644 to 0040755

The server exporting the filesystem is running 2.6.18.1 (knfsd) -
nothing is logged on the server...

So a file changed type and permissions out of the blue.  A few
questions about that:

Any way I can identify the file (or is it a dir now ;) ?
Does anyone know if this is a known bug that's been fixed? I couldn't
find anything via google or git that looked like a fix.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-02-26 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 13:31 Jesper Juhl [this message]
2007-02-26 13:31 ` nfs_update_inode: inode 309229856 mode changed, 0100644 to 0040755 - kernel 2.6.13.4 Jesper Juhl
2007-03-01  9:17 ` Jesper Juhl
2007-03-01  9:17   ` Jesper Juhl

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=9a8748490702260531h45a91113o611c272c0fe7b39f@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.