Bug 129132

Summary: [nfs] 7.1-Beta2 nfsd cannot lock
Product: Base System Reporter: Clarence CHU <clcchu>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed Overcome By Events    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Clarence CHU 2008-11-24 13:30:06 UTC 
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.

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
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
Comment 1 Remko Lodder 2008-11-24 14:59:31 UTC 
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
Comment 2 Clarence CHU 2008-11-24 17:50:54 UTC 


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
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:25 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2024-11-17 03:46:16 UTC 
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of suppoprt.
Please re-open if it is still a problem on a supported version.