From: Christian Reis <kiko@async.com.br>
To: Juergen Hasch <Hasch@t-online.de>
Cc: NFS@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] 2.4.19+trond and diskless locking problems
Date: Fri, 4 Oct 2002 10:17:12 -0300 [thread overview]
Message-ID: <20021004101712.A333@blackjesus.async.com.br> (raw)
In-Reply-To: <200210040907.47257.hasch@t-online.de>; from Hasch@t-online.de on Fri, Oct 04, 2002 at 09:07:47AM +0200
On Fri, Oct 04, 2002 at 09:07:47AM +0200, Juergen Hasch wrote:
> I got the same messages when mounting an AIX client to a Linux server after
> upgrading to 2.4.19 Kernel.
> After installing the latest NFS utils, the problem went away.
Does this mean nfs-utils-1.0.1 vs 1.0, or were you using a much older
version?
> So I guess Trond is right, try looking at the userspace utilities.
I will, thanks.
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
next prev parent reply other threads:[~2002-10-04 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 21:44 2.4.19+trond and diskless locking problems Christian Reis
2002-10-03 22:47 ` Trond Myklebust
2002-10-03 23:26 ` Christian Reis
2002-10-04 1:13 ` Trond Myklebust
2002-11-20 14:02 ` Christian Reis
2002-11-20 17:02 ` Trond Myklebust
2002-11-27 0:41 ` Christian Reis
2002-11-27 1:14 ` Trond Myklebust
2002-11-27 1:44 ` Christian Reis
2002-11-27 17:08 ` Christian Reis
2002-11-27 20:31 ` Trond Myklebust
2002-11-29 1:34 ` Christian Reis
2002-12-02 14:51 ` Christian Reis
[not found] ` <20021128232911.G18175@blackjesus.async.com.br>
[not found] ` <200212021921.24330.trond.myklebust@fys.uio.no>
2002-12-04 14:20 ` Christian Reis
2002-11-27 1:01 ` Christian Reis
2002-10-04 7:07 ` [NFS] " Juergen Hasch
2002-10-04 13:17 ` Christian Reis [this message]
2002-10-04 16:00 ` Juergen Hasch
2002-10-04 16:00 ` [NFS] " Juergen Hasch
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=20021004101712.A333@blackjesus.async.com.br \
--to=kiko@async.com.br \
--cc=Hasch@t-online.de \
--cc=NFS@lists.sourceforge.net \
--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 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.