From owner-freebsd-current Sun Aug 22 17:40:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mw5.texas.net (mw5.texas.net [206.127.30.15])
by hub.freebsd.org (Postfix) with ESMTP id 6B47B14F08
for <current@FreeBSD.ORG>; Sun, 22 Aug 1999 17:40:42 -0700 (PDT)
(envelope-from rsnow@lgc.com)
Received: from basil.dympna.COM (mnet07-78.sat.texas.net [209.99.53.78])
by mw5.texas.net (2.4/2.4) with ESMTP
id TAA20233; Sun, 22 Aug 1999 19:39:09 -0500 (CDT)
Received: from lgc.com (IDENT:rsnow@turbo [134.132.228.6])
by basil.dympna.COM (8.9.3/8.8.7) with ESMTP id TAA01262;
Sun, 22 Aug 1999 19:39:00 -0500 (CDT)
(envelope-from rsnow@lgc.com)
Message-ID: <37C09823.D36A0D7C@lgc.com>
Date: Sun, 22 Aug 1999 19:38:59 -0500
From: Rob Snow <rsnow@lgc.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.11 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Doug <Doug@gorean.org>, "John S. Dyson" <dyson@iquest.net>,
current@FreeBSD.ORG
Subject: Re: Patches available (was Re: NFS HEADS UP)
References: <199908222250.PAA77319@apollo.backplane.com> <37C0868D.33EDC140@lgc.com> <199908222346.QAA00694@apollo.backplane.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Anyways, I have to agree with you on the protocol issue. I cannot even
get mounts to work reliably between the Linux boxes, they seem to get
confused. Basically, looks like recent Linux NFS Server is broken,
therefore, I'm guessing that the error I saw was on that side of the
house.
FYI, my Bonnie numbers from Linux client look about the same as
pre-patch, in my initial tests.
-Rob
Matthew Dillon wrote:
>
> :linux> cp multipatch-1.diff test1
> :fbsd> cat test1
> :cat: test1: RPC struct is bad
> :fbsd> cp test1 /tmp
> :fbsd> cat test1
> :<SNIP>
> :+ (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) {
> :
> :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> :^@^@^@^@^@^@^@^@requested range. Note: we are assuming that
> :<SNIP>
> :
> :Doesn't happen between two linux boxen. (Both 2.2.11-NFSv3)
> :
> :-Rob
>
> Yah, but that doesn't mean much. What we have here is some sort of
> protocol confusion. Try an NFSv2 mount and see if that works.
>
> If the problem is protocol confusion there's a good 70% chance that the
> confusion is on the side of the linux server, since linux's NFSv3
> implementation is *very* recent. It would take someone with a protocol
> analyzer to track it down.
>
> -Matt
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message