From: Martin Zwickel <martin.zwickel@technotrend.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, apiszcz@lucidpixels.com
Subject: Re: Kernel 2.6.x: nfs warning: mount version older than kernel
Date: Fri, 22 Oct 2004 14:18:56 +0200 [thread overview]
Message-ID: <20041022141856.50d2b1a6@phoebee> (raw)
In-Reply-To: <Pine.LNX.4.61.0410220727120.514@p500>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Fri, 22 Oct 2004 07:29:46 -0400 (EDT)
Justin Piszcz <jpiszcz@lucidpixels.com> bubbled:
> # mount -a
> # dmesg | tail -n 5
> nfs warning: mount version older than kernel
> nfs warning: mount version older than kernel
> nfs warning: mount version older than kernel
> nfs warning: mount version older than kernel
> nfs warning: mount version older than kernel
> # mount --version
> mount: mount-2.12h
> #
>
> I am using the latest util-linux from the developers site, so I am
> curious, why do I get this warning in dmesg/ring-buffer?
>
> # ftp://ftp.win.tue.nl/pub/linux-local/utils/util-linux/
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I think it's about the nfs server/client versions, not the version
of mount.
--
MyExcuse:
We only support a 28000 bps connection.
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-22 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 11:29 Kernel 2.6.x: nfs warning: mount version older than kernel Justin Piszcz
2004-10-22 12:18 ` Martin Zwickel [this message]
2004-10-22 17:47 ` Trond Myklebust
2004-10-22 17:47 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-10-23 15:59 Nick Warne
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=20041022141856.50d2b1a6@phoebee \
--to=martin.zwickel@technotrend.de \
--cc=apiszcz@lucidpixels.com \
--cc=jpiszcz@lucidpixels.com \
--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