mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Peter Jansen <hpj@urpla.net>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: trond.myklebust@fys.uio.no, Neil Brown <neilb@cse.unsw.edu.au>,
	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 16:32:12 +0100	[thread overview]
Message-ID: <20020115153224.5B55513E2@shrek.lisa.de> (raw)
In-Reply-To: <20020115115019.89B55143B@shrek.lisa.de> <15428.6953.453942.415989@charged.uio.no> <15428.14268.730698.637522@laputa.namesys.com>
In-Reply-To: <15428.14268.730698.637522@laputa.namesys.com>

On Tuesday, 15. January 2002 15:07, Nikita Danilov wrote:
> 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?

I can reproduce it with 2.4.5, 6, 13-ac7, 18-pre3 with and without Trond's
NFS-ALL patches applied. I don't understand your question, but testing this
implied several reboots of the server and some dozen reboots on the client.

The lm_sensors build reproduced it pretty stable (with a few exceptions,
and on different commands of the range ar, gcc and ln)
Test is pretty simple: clean make of lm_sensors almost all the time 
triggers it. If not, just rm lib/libsensors* and make again. This
created certainly stale files lib/libsensors.so|lib/libsensors.so.1
from within the client. You can only get rid of them by rebooting or
removing them on the server.

>  > 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).

Please, try to reproduce it, and let us know, if you can reproduce it.

>  > Cheers,
>  >   Trond
>
> Nikita.

Cheers,
  Hans-Peter

      parent reply	other threads:[~2002-01-15 15:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 14:07 Nikita Danilov
2002-01-15 11:50 ` Hans-Peter Jansen
2002-01-15 12:06   ` Trond Myklebust
2002-01-15 13:40     ` Trond Myklebust
2002-01-15 13:40   ` David L. Parsley
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 18:14       ` Hans-Peter Jansen
2002-01-15 19:25       ` Nikita Danilov
2002-01-15 19:30       ` Nikita Danilov
2002-01-15 15:32 ` Hans-Peter Jansen [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=20020115153224.5B55513E2@shrek.lisa.de \
    --to=hpj@urpla.net \
    --cc=Nikita@Namesys.COM \
    --cc=Reiserfs-List@Namesys.COM \
    --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

all inboxes | Powered by JetHome®