On Wednesday March 5, [email protected] wrote:
> Neil Brown wrote:
> > On Wednesday March 5, [email protected] wrote:
> >
> > Where :-)
> >
> > A excerpt from the logs to show actual error messages could be
> > helpful.
> >
> > Thanks,
> > NeilBrown
> sorry, must have missed the paste
>
> Feb 28 17:27:58 koi kernel: nfs_update_inode: inode 3221350147 mode
> changed, 0040755 to 0100644
> Feb 28 21:57:22 koi kernel: nfs_update_inode: inode 2149056279 mode
> changed, 0040755 to 0100755
> Mar 5 01:43:21 koi kernel: nfs_update_inode: inode 3222473680 mode
> changed, 0040755 to 0100644
> Mar 5 08:52:19 koi kernel: nfs_update_inode: inode 3222473568 mode
> changed, 0120777 to 0100644
> Mar 5 15:00:01 koi kernel: nfs_update_inode: inode 3222473569 mode
> changed, 0120777 to 0100644
> Mar 5 15:00:31 koi kernel: nfs_update_inode: inode 3222473674 mode
> changed, 0120777 to 0100644
> Mar 5 15:00:31 koi kernel: nfs_update_inode: inode 3222473675 mode
> changed, 0120777 to 0100644
> Mar 5 15:00:31 koi kernel: nfs_update_inode: inode 3222473672 mode
> changed, 0040755 to 0100644
> Mar 5 15:00:31 koi kernel: nfs_update_inode: inode 3222473673 mode
> changed, 0120777 to 0100644
>
>
Hmmm...
Directories and symlinks "changing" to regular files.
32bit inode numbers with the high bit set.
Random times, but a burst at 3pm one afternoon.
The fact that it happens so rarely make is very hard to collect more
data....
What happens when a user experiences an error? What sort of file is
the error reported against? Does the file remain inaccessible or does
it start working again soon? Is the same file accessible from another
client?
NeilBrown