public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: trond.myklebust@fys.uio.no
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Hans-Peter Jansen <hpj@urpla.net>,
	linux-kernel@vger.kernel.org,
	Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [BUG] symlink problem with knfsd and reiserfs
Date: Tue, 15 Jan 2002 17:07:56 +0300	[thread overview]
Message-ID: <15428.14268.730698.637522@laputa.namesys.com> (raw)
In-Reply-To: <15428.6953.453942.415989@charged.uio.no>
In-Reply-To: <20020115115019.89B55143B@shrek.lisa.de> <15428.6953.453942.415989@charged.uio.no>

Trond Myklebust writes:
 > >>>>> " " == Hans-Peter Jansen <hpj@urpla.net> writes:
 > 
 >      > In syslog, this message appears: Jan 15 00:21:03 elfe kernel:
 >      > nfs_refresh_inode: inode 50066 mode changed, 0100664 to 0120777
 > 
 > The error is basically telling you that ReiserFS filehandles are being
 > reused by the server. Doesn't Reiser provide a generation count to
 > guard against this sort of thing?

Yes, inode->i_generation is stored in the file handle:
fs/reiserfs/inode.c:reiserfs_dentry_to_fh().

Hans-Peter, what version of NFS are you using and have you remounted
clients after upgrading to the newer kernel?

 > 
 > My 'fix' just solves the immediate problem of the wrong file mode. It
 > does not solve the problems of data corruption that can occur when the
 > client is incapable of distinguishing the 'old' and 'new' files that
 > share the same filehandle.

This requires i_generation overflow (modulo bug in reiserfs).

 > 
 > Cheers,
 >   Trond

Nikita.

  reply	other threads:[~2002-01-15 13:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 11:50 [BUG] symlink problem with knfsd and reiserfs Hans-Peter Jansen
2002-01-15 12:06 ` Trond Myklebust
2002-01-15 14:07   ` Nikita Danilov [this message]
2002-01-15 13:40     ` Trond Myklebust
2002-01-15 15:27       ` Nikita Danilov
2002-01-15 15:38         ` Trond Myklebust
2002-01-15 16:47           ` Nikita Danilov
2002-01-15 16:31             ` Hans-Peter Jansen
2002-01-15 17:53               ` Nikita Danilov
2002-01-15 18:01                 ` David L. Parsley
2002-01-15 19:30                   ` Nikita Danilov
2002-01-15 18:14                 ` Hans-Peter Jansen
2002-01-15 19:25                   ` Nikita Danilov
2002-01-15 15:32     ` Hans-Peter Jansen
2002-01-15 13:40 ` David L. Parsley

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=15428.14268.730698.637522@laputa.namesys.com \
    --to=nikita@namesys.com \
    --cc=Reiserfs-List@Namesys.COM \
    --cc=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=trond.myklebust@fys.uio.no \
    /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