All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: nfs@lists.sourceforge.net
Subject: Re: Mount version older than kernel: 4 vs. 6
Date: Wed, 04 Aug 2004 15:25:23 +0200	[thread overview]
Message-ID: <4110E3C3.3050705@bio.ifi.lmu.de> (raw)
In-Reply-To: <20040804130419.GI4471@suse.de>

Olaf Kirch wrote:
> On Wed, Aug 04, 2004 at 02:50:09PM +0200, Frank Steiner wrote:
> 
>>Just a stupid question: why does the nfsmount.h from the kernel source
>>define NFS_MOUNT_VERSION 6? Shouldn't this number match the latest nfs
>>version, i.e., 4? I've never heard of nfs v6 yet :-)
>>Or is the meaning of NFS_MOUNT_VERSION different?
> 
> 
> That's the version of the NFS kernel mount struct, and is
> absolutely unrelated to the NFS version (except that both
> grow monotonically over time).

I see. But then it looks like a bug to me that the code in the inode.c
is comparing the "NFS version" (4, in data->version) against the
"NFS kernel mount struct" (6, in NFS_MOUNT_VERSION). That doesn't
make sense, does it?

I added this to inode.c
         if (data->version != NFS_MOUNT_VERSION) {
                 printk("nfs warning: mount version %s than kernel\n",
                         data->version < NFS_MOUNT_VERSION ? "older" : "newer");
+                printk("data version: %d\n",data->version);
+                printk("NFS_MOUNT_VERSION: %d\n",NFS_MOUNT_VERSION);


and got this result:
Aug  4 14:33:50 riemann kernel: nfs warning: mmmount version older than kernel
Aug  4 14:33:50 riemann kernel: data version: 4
Aug  4 14:33:50 riemann kernel: NFS_MOUNT_VERSION: 6


cu,
Frank


-- 
Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik    Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17           Phone: +49 89 2180-4049
80333 Muenchen, Germany       Fax:   +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-08-04 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 12:50 Mount version older than kernel: 4 vs. 6 Frank Steiner
2004-08-04 13:04 ` Olaf Kirch
2004-08-04 13:25   ` Frank Steiner [this message]
2004-08-04 13:51     ` Olaf Kirch
2004-08-04 21:34       ` Trond Myklebust

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=4110E3C3.3050705@bio.ifi.lmu.de \
    --to=fsteiner-mail@bio.ifi.lmu.de \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.