From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: nfs@lists.sourceforge.net
Subject: Mount version older than kernel: 4 vs. 6
Date: Wed, 04 Aug 2004 14:50:09 +0200 [thread overview]
Message-ID: <4110DB81.4020103@bio.ifi.lmu.de> (raw)
Hi,
using kernel 2.6.8rc3 and util-linux-2.12a, I ran into those "mount
version older than kernel" messages, which were discussed here for the
2.6.4 kernel before. Patching inode.c, I can see that NFS_MOUNT_VERSION
is 6, while data->version is 4. (The only mount at all that does not
complain is the one done by nfsroot (of course) :-))
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?
Would it be safe to patch nfsmount.h and set the number to 4 for my
own kernel to get rid of this warning, or could that break sth. else?
It just fills my logs and I want to get rid of it...
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
next reply other threads:[~2004-08-04 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 12:50 Frank Steiner [this message]
2004-08-04 13:04 ` Mount version older than kernel: 4 vs. 6 Olaf Kirch
2004-08-04 13:25 ` Frank Steiner
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=4110DB81.4020103@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.