kern/129132: 7.1-Beta2 nfsd cannot lock

Clarence Chu clcchu at hotmail.com
Mon Nov 24 10:10:10 PST 2008


The following reply was made to PR kern/129132; it has been noted by GNATS.

From: Clarence Chu <clcchu at hotmail.com>
To: <remko at elvandar.org>
Cc: <freebsd-gnats-submit at freebsd.org>, <dfr at 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_--


More information about the freebsd-bugs mailing list