Date: Sat, 19 Mar 2005 12:41:37 -0500 From: "Philip M. Golllucci" <pgollucci@p6m7g8.com> To: Dominique Goncalves <dominique.goncalves@gmail.com> Cc: questions@freebsd.org Subject: Re: NFS and file locking Message-ID: <423C6451.7030805@p6m7g8.com> In-Reply-To: <7daacbbe05031909236b7acc85@mail.gmail.com> References: <423C567A.1040102@p6m7g8.com> <7daacbbe05031909236b7acc85@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, That works! I haven't tried it yet...., but is it better to use the -L or run these 3 services ? Also, if anyone knows how to add this in fstab that would be nice too... Not that I reboot that often :) Thanks! -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. END ------------------------------------------------------------------------------ Philip M. Gollucci Consultant E-Mail: pgollucci@p6m7g8.com URL : http://p6m7g8.net/Resume/resume.shtml Phone : 301.254.5198 $Id: .signature,v 1.7 2004/09/05 23:46:37 philip Exp $ Dominique Goncalves wrote: > Hi, > > I had exactly same problem, to resolve this, use the -L option of mount_nfs. > But I don't know how can I add this option in /etc/fstab. > > Hope this help. > > Regards. > > > On Sat, 19 Mar 2005 11:42:34 -0500, Philip M. Golllucci > <pgollucci@p6m7g8.com> wrote: > >>Hi all, >> >>I've got a FreeBSD 6.x -current file server running NFS and I mount >>lots of things via NFS on other Freebsd 6.x -current servers with an NFS >>client. I get _lots_ of file locking issues. See below for just one >>example. I'm wondering, will NFSv4 fix this or switching to samba ? >>If not, I'd be gratefull for suggestions. >> >>Thanks in advance! >> >>vegeta# df >>krillin:/usr/ports 15390126 3159612 10999304 22% /usr/ports >>krillin:/usr/local/apps 15390126 3159612 10999304 22% /usr/local/apps >>krillin:/usr/src 15390126 3159612 10999304 22% /usr/src >>krillin:/usr/obj 15390126 3159612 10999304 22% /usr/obj >>krillin:/usr/home 15390126 3159612 10999304 22% /usr/home >> >>vegeta# cd /usr/ports/www/apache21/ >>vegeta# make >>[......] >>buildconf: Using libtool15.m4 at /usr/local/share/aclocal/libtool15.m4. >>Creating include/arch/unix/apr_private.h.in ... >>autom4te259: cannot lock autom4te.cache/requests with mode 2 (perhaps >>you are running make -j on a lame NFS client?): Operation not supported >>autoheader259: /usr/local/bin/autom4te259 failed with exit status: 1 >>Creating configure ... >>autom4te259: cannot lock autom4te.cache/requests with mode 2 (perhaps >>you are running make -j on a lame NFS client?): Operation not supported >>Generating 'make' outputs ... >>rebuilding rpm spec file >>rebuilding srclib/apr-util/configure >> >>Looking for apr source in ../apr >>Creating include/private/apu_config.h ... >>autom4te259: cannot lock autom4te.cache/requests with mode 2 (perhaps >>you are running make -j on a lame NFS client?): Operation not supported >>autoheader259: /usr/local/bin/autom4te259 failed with exit status: 1 >>./buildconf failed for apr-util >> >>-- >>END >>------------------------------------------------------------------------------ >> >>Philip M. Gollucci >>Consultant >>E-Mail: pgollucci@p6m7g8.com >>URL : http://p6m7g8.net/Resume/resume.shtml >>Phone : 301.254.5198 >> >>$Id: .signature,v 1.7 2004/09/05 23:46:37 philip Exp $ >> >>_______________________________________________ >>freebsd-questions@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >> > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?423C6451.7030805>