lkml.org 
[lkml]   [2006]   [Dec]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [2.6.19] NFS: server error: fileid changed
From
Date
On Fri, 2006-12-15 at 09:16 -0800, Martin Knoblauch wrote:
> --- Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> >
> > > Is there a way to find out which files are involved? Nothing
> > seems to
> > > be obviously breaking, but I do not like to get my logfiles filled
> > up.
> >
> > The fileid is the same as the inode number. Just convert those
> > hexadecimal values into ordinary numbers, then search for them using
> > 'ls
> > -i'.
> >
> > Trond
> >
> > > [ 9337.747546] NFS: server nvgm022 error: fileid changed
> > > [ 9337.747549] fsid 0:25: expected fileid 0x7a6f3d, got 0x65be80
> Hi Trond,
>
> just curious: how is the fsid related to mounted filesystems? What
> does "0:25" stand for?
>

In this case the fsid is just the major:minor device numbers assigned to
that filesystem.
Look for it using 'stat -printf "%D\n" /mountpoint'

Cheers
Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-12-15 20:33    [W:0.141 / U:0.156 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site