mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: knobi@knobisoft.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.19] NFS: server error: fileid changed
Date: Fri, 15 Dec 2006 14:30:14 -0500	[thread overview]
Message-ID: <1166211014.5761.46.camel@lade.trondhjem.org> (raw)
In-Reply-To: <801847.80879.qm@web32613.mail.mud.yahoo.com>

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


      reply	other threads:[~2006-12-15 19:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 16:09 Martin Knoblauch
2006-12-11 17:23 ` Trond Myklebust
2006-12-11 23:44   ` Martin Knoblauch
2006-12-12  0:25     ` Trond Myklebust
2006-12-12  3:16       ` Martin Knoblauch
2006-12-15 17:16   ` Martin Knoblauch
2006-12-15 19:30     ` Trond Myklebust [this message]

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=1166211014.5761.46.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=knobi@knobisoft.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®