Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z

[Adam Schrotenboer]

Neil Brown wrote:
> On Wednesday March 5, adam@xxxxxxxxx wrote:
>   
> > Neil Brown wrote:
> >     
> > > On Wednesday March 5, adam@xxxxxxxxx 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? 
well, sometimes it shows up as a read/write error (that is the error 
code returned by the application).
SVN tend to be more verbose (although I have no examples)
>  What sort of file is
> the error reported against?  
It does not to my knowledge only happen to certain classes of files, 
although it does seem to happen most often when lots of files are being 
created.
> Does the file remain inaccessible or does
> it start working again soon?  
No data, maybe Thomas knows something.
> Is the same file accessible from another
> client?
>   
No data, esp as it never happens to me personally.
> NeilBrown
>

Attachment: signature.asc
Description: OpenPGP digital signature