From: Vince Busam <vbusam@google.com>
To: nfs@lists.sourceforge.net
Subject: fileid changed messages appearing after upgrade to 2.6.16.1
Date: Tue, 11 Apr 2006 19:45:31 -0700 [thread overview]
Message-ID: <443C69CB.4060503@google.com> (raw)
After upgrading from 2.6.13.4 + CITI NFS patch to 2.6.16.1 (with no
patches), I've started seeing error messages like the following:
NFS: server build.nfs error: fileid changed
fsid 0:17: expected fileid 0x5d3644, got 0x5d363c
nfs_update_inode: inode 6108740 mode changed, 0040755 to 0000000
The equivalent errors (the printk output was moved and changed) did not
show up with 2.6.13.4. Is this a known issue, or is there anything I
can do to help pinpoint the problem?
Thanks,
Vince
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2006-04-12 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 2:45 Vince Busam [this message]
2006-04-12 3:10 ` fileid changed messages appearing after upgrade to 2.6.16.1 Trond Myklebust
2006-04-12 4:13 ` Vince Busam
2006-04-12 5:59 ` Trond Myklebust
2006-04-13 0:52 ` Vince Busam
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=443C69CB.4060503@google.com \
--to=vbusam@google.com \
--cc=nfs@lists.sourceforge.net \
/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.