Re: errno (46) - for FreeBSD 4.0 NFS server
Thierry, thank you for the information, but it's very bad that there isn't NFS locking in FreeBSD. I'm afraid I need to move my FreeBSD NFS server to Solaris for x86. I don't understand why NFS locking isn't in FreeBSD. Is it difficult in the implementation or are there another global problems in the kernel (or in the native filesystem)? Who know when the NFS locking is planed to release in FreeBSD? Grigory. On Tue, 21 Mar 2000 [EMAIL PROTECTED] wrote: Hello, There is presently *NO* NFS locking in FreeBSD (for all versions). There will be some NFS locking in the near future - stay tuned. TfH Grigory Kljuchnikov [EMAIL PROTECTED] on 21/03/2000 17:16:08 Hello! I have a FreeBSD 4.0 NFS server and get an error message (No record locks available - errno (46)) when a HP-UX 10.20 client run some compilation process (with make) on the NFS-mounted file system that is reside on that FreeBSD 4.0 NFS server. This error appear on the HP-UX 10.20 NFS-client host. If I use Solaris 2.6 NFS server in same circumstance I don't have that error. What is wrong? or What are the kernel parameters I need to change on FreeBSD? Grigory Kljuchnikov Institute for System Programming Russian Academy of Sciences, 109004, Moscow, Russia, B.Kommunistitcheskay, 25, phone(work): +7-095-9125659 fax: +7-095-9121524 e-mail:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: errno (46) - for FreeBSD 4.0 NFS server
On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote: Thierry, thank you for the information, but it's very bad that there isn't NFS locking in FreeBSD. I'm afraid I need to move my FreeBSD NFS server to Solaris for x86. I don't understand why NFS locking isn't in FreeBSD. Is it difficult in the implementation or are there another global problems in the kernel (or in the native filesystem)? Who know when the NFS locking is planed to release in FreeBSD? Actually I think that server side locking *is* implemented but client side locking isn't. 'man 8 rpc.lockd' for more information. (And 'man 5 rc.conf' for information on how to start it at bootup. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: errno (46) - for FreeBSD 4.0 NFS server
Thank you, Erik! I find rpc.lockd and start it manually. My test with NFS locking works right. But it don't start on boot by default if I enable NFS server in /stand/sysinstall and there is the comment in /etc/default/rc.conf for rpc_lockd_enable: rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. Does the comment "(*broken!*)" mean that rpc.lockd doesn't work properly? Grigory. On Wed, 22 Mar 2000, Erik Trulsson wrote: On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote: Thierry, thank you for the information, but it's very bad that there isn't NFS locking in FreeBSD. I'm afraid I need to move my FreeBSD NFS server to Solaris for x86. I don't understand why NFS locking isn't in FreeBSD. Is it difficult in the implementation or are there another global problems in the kernel (or in the native filesystem)? Who know when the NFS locking is planed to release in FreeBSD? Actually I think that server side locking *is* implemented but client side locking isn't. 'man 8 rpc.lockd' for more information. (And 'man 5 rc.conf' for information on how to start it at bootup. Grigory Kljuchnikov Institute for System Programming Russian Academy of Sciences, 109004, Moscow, Russia, B.Kommunistitcheskay, 25, phone(work): +7-095-9125659 fax: +7-095-9121524 e-mail:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: errno (46) - for FreeBSD 4.0 NFS server
On Wed, Mar 22, 2000 at 03:46:12PM +0300, Grigory Kljuchnikov wrote: Thank you, Erik! I find rpc.lockd and start it manually. My test with NFS locking works right. But it don't start on boot by default if I enable NFS server in /stand/sysinstall and there is the comment in /etc/default/rc.conf for rpc_lockd_enable: rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. Does the comment "(*broken!*)" mean that rpc.lockd doesn't work properly? To be honest I don't know. I haven't used it myself but only read the manpages. (Since I only use NFS between FreeBSD boxes and they don't support client-side locking it seems pointless to have it on the server.) That comment does seem to imply that something is broken but then the manpage really should say something about that. (This might of course indicate that the manpage isn't in sync with reality.) Somebody who knows what is up with rpc.lockd is welcome to comment. On Wed, 22 Mar 2000, Erik Trulsson wrote: On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote: Thierry, thank you for the information, but it's very bad that there isn't NFS locking in FreeBSD. I'm afraid I need to move my FreeBSD NFS server to Solaris for x86. I don't understand why NFS locking isn't in FreeBSD. Is it difficult in the implementation or are there another global problems in the kernel (or in the native filesystem)? Who know when the NFS locking is planed to release in FreeBSD? Actually I think that server side locking *is* implemented but client side locking isn't. 'man 8 rpc.lockd' for more information. (And 'man 5 rc.conf' for information on how to start it at bootup. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: errno (46) - for FreeBSD 4.0 NFS server
I believe the lockd daemon is used in environments where applications at the client end will not work unless they can make a lock call and get a positive result.. so in environments where you feel its fairly safe to fake a lock to a client app, in order to get the app working at all, that you would use this. (At least I think that used to be the reason for it) On Wed, 22 Mar 2000, Erik Trulsson wrote: On Wed, Mar 22, 2000 at 03:46:12PM +0300, Grigory Kljuchnikov wrote: Thank you, Erik! I find rpc.lockd and start it manually. My test with NFS locking works right. But it don't start on boot by default if I enable NFS server in /stand/sysinstall and there is the comment in /etc/default/rc.conf for rpc_lockd_enable: rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. Does the comment "(*broken!*)" mean that rpc.lockd doesn't work properly? To be honest I don't know. I haven't used it myself but only read the manpages. (Since I only use NFS between FreeBSD boxes and they don't support client-side locking it seems pointless to have it on the server.) That comment does seem to imply that something is broken but then the manpage really should say something about that. (This might of course indicate that the manpage isn't in sync with reality.) Somebody who knows what is up with rpc.lockd is welcome to comment. On Wed, 22 Mar 2000, Erik Trulsson wrote: On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote: Thierry, thank you for the information, but it's very bad that there isn't NFS locking in FreeBSD. I'm afraid I need to move my FreeBSD NFS server to Solaris for x86. I don't understand why NFS locking isn't in FreeBSD. Is it difficult in the implementation or are there another global problems in the kernel (or in the native filesystem)? Who know when the NFS locking is planed to release in FreeBSD? Actually I think that server side locking *is* implemented but client side locking isn't. 'man 8 rpc.lockd' for more information. (And 'man 5 rc.conf' for information on how to start it at bootup. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: errno (46) - for FreeBSD 4.0 NFS server
On Wed, Mar 22, 2000 at 05:51:18PM +0100, Erik Trulsson wrote: Somebody who knows what is up with rpc.lockd is welcome to comment. AFAIK the lockd code just says "Sure - have a lock" to any request. I think David Cross and some other people have a half working lockd now, they were looking for people to play with it on the list only a couple of weeks ago. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: errno (46) - for FreeBSD 4.0 NFS server
Grigory Kljuchnikov stated: Thank you, Erik! I find rpc.lockd and start it manually. My test with NFS locking works right. But it don't start on boot by default if I enable NFS server in /stand/sysinstall and there is the comment in /etc/default/rc.conf for rpc_lockd_enable: rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. Does the comment "(*broken!*)" mean that rpc.lockd doesn't work properly? Grigory. On Wed, 22 Mar 2000, Erik Trulsson wrote: On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote: Thierry, thank you for the information, but it's very bad that there isn't NFS locking in FreeBSD. I'm afraid I need to move my FreeBSD NFS server to Solaris for x86. I don't understand why NFS locking isn't in FreeBSD. Is it difficult in the implementation or are there another global problems in the kernel (or in the native filesystem)? Who know when the NFS locking is planed to release in FreeBSD? Actually I think that server side locking *is* implemented but client side locking isn't. 'man 8 rpc.lockd' for more information. (And 'man 5 rc.conf' for information on how to start it at bootup. Grigory- My understanding of the current implementation of rpc.lockd is that it is a facade and simply tells the client requesting a lock "sure kid, you have a lock" and then does nothing. "David E. Cross" [EMAIL PROTECTED] has been working to implement a real server-side rpc.lockd. You may want to contact him. The first go 'round failed the nfs connectathon tests, but the second version purportedly addresses these issues with all but SGI boxen. However, it was delayed pending some system header changes... wild_speculation Since the merger with BSDi, FreeBSD hopefully will be getting both client and server-side locking (of course, this will appear first in 5.0-CURRENT at some point) along with some nice SMP support (fingers firmly crossed). /wild_speculation Hope this helps, S --- Sean O'ConnellEmail: [EMAIL PROTECTED] Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
