From nobody@FreeBSD.org  Mon Nov 24 13:27:24 2008
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CD715106564A
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 24 Nov 2008 13:27:24 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id BF1118FC29
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 24 Nov 2008 13:27:24 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mAODROPg091503
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 24 Nov 2008 13:27:24 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id mAODROH2091497;
	Mon, 24 Nov 2008 13:27:24 GMT
	(envelope-from nobody)
Message-Id: <200811241327.mAODROH2091497@www.freebsd.org>
Date: Mon, 24 Nov 2008 13:27:24 GMT
From: Clarence CHU <clcchu@hotmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: 7.1-Beta2  nfsd cannot lock
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         129132
>Category:       kern
>Synopsis:       [nfs] 7.1-Beta2 nfsd cannot lock
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 24 13:30:06 UTC 2008
>Closed-Date:    
>Last-Modified:  Mon Nov 24 18:10:07 UTC 2008
>Originator:     Clarence CHU
>Release:        7.1-Beta2
>Organization:
Data Expert Limited
>Environment:
FreeBSD freebsd.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Nov 24 19:09:59 HKT 2008     root@freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386
>Description:

when an exported /usr/local/openoffice.org-3.0.0 was mounted from
7.1-PRERELEASE share, andthe client is running the same version
of 7.1-PRERELEASE, it complain about "Component Manager not found"

remedial is to use mount_nfs -L from the clients.

when the share is on 7.0-RELEASE-p5 _OR_ opensolaris.org snv_101,
the problem doesn't exist.

>How-To-Repeat:

from the client running 7.1-PRERELEASE, mount another node
running the same system of /usr/local with OOo3 using, say,

mount nfsserv:/usr/local /usr/local; ldconfig -m /usr/local/lib

running openoffice.org-3.0.0 will core dump with "Component manager not found"
message.

if using: mount -L nfsserv:/usr/local /usr/local; ldconfig -m /usr/local/lib
proble vanish
>Fix:

1) if using: mount -L nfsserv:/usr/local /usr/local; ldconfig -m /usr/local/lib
problem vanish

2) fall back to 7.0-RELEASE-p5

3) Use another version of nfs server, such as solaris

>Release-Note:
>Audit-Trail:

From: "Remko Lodder" <remko@elvandar.org>
To: "Clarence CHU" <clcchu@hotmail.com>
Cc: freebsd-gnats-submit@freebsd.org,
 dfr@FreeBSD.org
Subject: Re: kern/129132: 7.1-Beta2  nfsd cannot lock
Date: Mon, 24 Nov 2008 15:59:31 +0100 (CET)

 On Mon, November 24, 2008 2:27 pm, Clarence CHU wrote:
 
 For clarity's sake:
 
 I assume you read the manual page and noticed this;
 
      -L      Do not forward fcntl(2) locks over the wire.  All locks will be
              local and not seen by the server and likewise not seen by other
              NFS clients.  This removes the need to run the rpcbind(8)
 service
              and the rpc.statd(8) and rpc.lockd(8) servers on the client.
              Note that this option will only be honored when performing the
              initial mount, it will be silently ignored if used while
 updating
              the mount options.
 
 
 Which results in the question: do you have rpc.statd and rpc.lockd running
 on the machine?
 
 I copied in Doug Rabson, who did a lot of work on NFS recently and might
 have more information wrt. Locking etc. (or not, then I was mistaken).
 
 thanks for sending the info and taking the time to report this! It's
 appreciated!
 
 -- 
 /"\   Best regards,                      | remko@FreeBSD.org
 \ /   Remko Lodder                       | remko@EFnet
  X    http://www.evilcoder.org/          |
 / \   ASCII Ribbon Campaign              | Against HTML Mail and News
 
 

From: Clarence Chu <clcchu@hotmail.com>
To: <remko@elvandar.org>
Cc: <freebsd-gnats-submit@freebsd.org>, <dfr@freebsd.org>
Subject: RE: kern/129132: 7.1-Beta2  nfsd cannot lock
Date: Tue, 25 Nov 2008 01:50:54 +0800

 --_65d8bc99-85e7-4783-a5c6-8c11502bcac6_
 Content-Type: text/plain; charset="big5"
 Content-Transfer-Encoding: 8bit
 
 
 
 
 Dear Remko,
 
 > 
 > Which results in the question: do you have rpc.statd and rpc.lockd running
 > on the machine?
 >
 
 definitely I had started rpc.statd and rpc.lockd, what appears strange to
 me is the setting when flipped between 7.0-p5 and 7.1-BETA2 behave
 differently (via #  make installworld; make installkernel; reboot).  so,
 I can assure you that it is not my server setting issue.
 
 I had actually spare a box for the test and report it as FreeBSD
 is the only FOSS doing well with lockd other than Solaris.
 Yes, _ALL_ linuxes failed that, AFAIK.
 
 I had switched to 7.1-PRERELEASE for a while and am to upgrade all
 my nodes (about 20) to 7.1 soon.
 
 > 
 > I copied in Doug Rabson, who did a lot of work on NFS recently and might
 > have more information wrt. Locking etc. (or not, then I was mistaken).
 > 
 
 
 well, the senerio is repeatable as described in the PR, too.
 
 Will watch for csup logs for any delta to nfs-related code.
 
 Also, I'm not sure, three of my SMP/Core2duo nodes failed
 to "make buildworld; make installworld" both for i386 and
 amd64, the cc generated dump core, and seems no problems
 for UP systems.
 
 the numerous device drivers additions and CTF capability is
 attractive, provided -RCs are more reliable than the -BETAs.
 
 Best wishes,
 
 Clarence CHU
 
 
 _________________________________________________________________
 Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
 http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
 --_65d8bc99-85e7-4783-a5c6-8c11502bcac6_
 Content-Type: text/html; charset="big5"
 Content-Transfer-Encoding: 8bit
 
 <html>
 <head>
 <style>
 .hmmessage P
 {
 margin:0px;
 padding:0px
 }
 body.hmmessage
 {
 font-size: 10pt;
 font-family:Verdana
 }
 </style>
 </head>
 <body class='hmmessage'>
 <br><br>Dear Remko,<br><br>&gt; <br>&gt; Which results in the question: do you have rpc.statd and rpc.lockd running<br>&gt; on the machine?<br>&gt;<br><br>definitely I had started rpc.statd and rpc.lockd, what appears strange to<br>me is the setting when flipped between 7.0-p5 and 7.1-BETA2 behave<br>differently (via #&nbsp; make installworld; make installkernel; reboot).&nbsp; so,<br>I can assure you that it is not my server setting issue.<br><br>I had actually spare a box for the test and report it as Fr eeBSD<br>is the only FOSS doing well with lockd other than Solaris.<br>Yes, _ALL_ linuxes failed that, AFAIK.<br><br>I had switched to 7.1-PRERELEASE for a while and am to upgrade all<br>my nodes (about 20) to 7.1 soon.<br><br>&gt; <br>&gt; I copied in Doug Rabson, who did a lot of work on NFS recently and might<br>&gt; have more information wrt. Locking etc. (or not, then I was mistaken).<br>&gt; <br><br><br>well, the senerio is repeatable as described in the PR, too.<br><b
  r>Will watch for csup logs for any delta to nfs-related code.<br><br>Also, I'm not sure, three of my SMP/Core2duo nodes failed<br>to "make buildworld; make installworld" both for i386 and<br>amd64, the cc generated dump core, and seems no problems<br>for UP systems.<br><br>the numerous device drivers additions and CTF capability is<br>attractive, provided -RCs are more reliable than the -BETAs.<br><br>Best wishes,<br><br>Clarence CHU<br><br><br /><hr />Invite your mail contacts to join your friends list w ith Windows Live Spaces. It's easy! <a href='http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us' target='_new'>Try it!</a></body>
 </html>
 --_65d8bc99-85e7-4783-a5c6-8c11502bcac6_--
>Unformatted:
