Re: newnfs user setup
On Sun, Sep 4, 2011 at 9:28 AM, Brandon Gooch wrote: > On Fri, Sep 02, 2011 at 08:25:05PM -0400, Rick Macklem wrote: >> Brandon Gooch wrote: >> > On Thu, Sep 1, 2011 at 8:09 PM, Brandon Gooch >> > wrote: >> > > On Fri, May 27, 2011 at 8:09 AM, Rick Macklem >> > > wrote: >> > >>> On Thu, 26 May 2011, Rick Macklem wrote: >> > >>> ... >> > >>> > ??http://people.freebsd.org/~rmacklem/dtrace.patch >> > >>> > >> > >>> Hmm. Is it just me? >> > >>> Trying to test the patch I get: >> > >>> >> > >>> (fs)(root) patch -C < dtrace.patch >> > >>> Hmm... I can't seem to find a patch in there anywhere. >> > >>> >> > >> Here's how I apply the patch. >> > >> - download dtrace.patch to somewhere, lets say /tmp, then >> > >> # cd /usr/src/sys <-- sys subdirectory of a current head, >> > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? which you don't mind messing up >> > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? doesn't have to be at /usr/src/sys, >> > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? of course. >> > >> # patch -p1 < /tmp/dtrace.patch >> > >> >> > >> rick >> > >> >> > > >> > > What's the status on this patch? It would be nice to get >> > > dtrace/newnfs >> > > going for 9.0...it's not too late, right? >> > > >> > > I'll test the patch too BTW :) >> > > >> > > -Brandon >> > > >> > >> > So it looks like the patch was committed to HEAD, but the bits to >> > support the New NFS implementation were never flipped on -- is that >> > for a good reason? >> > >> I know nothing about Dtrace, so if something needs to be changed/fixed, >> someone who understands these things will have to let me know. >> >> When I built a kernel with "options KDTRACE_HOOKS" and set >> dtraceall_load="YES" in /etc/rc.conf, >> it booted and >> # dtrace -l >> - seemed to find the stuff (it's called "dtnfscl", btw). >> >> Someone told me that's how you check it's loaded and that's all I >> know how to do w.r.t. dtrace. >> >> If you can test/debug it, that would be great, rick > > Actually, the problem is not with DTrace functioning, but with the > dtnfsclient.ko module: > > brandon@m6500:~$ sudo kldload dtnfsclient > kldload: can't load dtnfsclient: Exec format error > > brandon@m6500:~$ dmesg > ... > link_elf_obj: symbol nfsclient_accesscache_flush_done_id undefined > linker_load_file: Unsupported file type > ... After fixing a DTrace module related build bug (see kern/160463), I was able to build and install dtrace and both the old and new NFS client dtrace providers were loaded: $ sudo dtrace -l | grep nfs | wc -l 2472 $ kldstat -v | grep dtnfs 22 1 0x8133d000 57ca dtnfscl.ko (/boot/kernel/dtnfscl.ko) 234 dtnfscl 24 1 0x81385000 4f64 dtnfsclient.ko (/boot/kernel/dtnfsclient.ko) 237 dtnfsclient Be sure to read through what's required to get DTrace going from the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/dtrace-enable.html . > Any hints on debugging undefined symbols? This is a runtime linker error because it can't find the symbol -- in particular if you don't define some of the required options (like DDB_CTF, WITH_CTF=1), things don't load too terribly well. HTH, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
Brandon Gooch wrote: > On Fri, Sep 02, 2011 at 08:25:05PM -0400, Rick Macklem wrote: > > Brandon Gooch wrote: > > > On Thu, Sep 1, 2011 at 8:09 PM, Brandon Gooch > > > wrote: > > > > On Fri, May 27, 2011 at 8:09 AM, Rick Macklem > > > > > > > > wrote: > > > >>> On Thu, 26 May 2011, Rick Macklem wrote: > > > >>> ... > > > >>> > ??http://people.freebsd.org/~rmacklem/dtrace.patch > > > >>> > > > > >>> Hmm. Is it just me? > > > >>> Trying to test the patch I get: > > > >>> > > > >>> (fs)(root) patch -C < dtrace.patch > > > >>> Hmm... I can't seem to find a patch in there anywhere. > > > >>> > > > >> Here's how I apply the patch. > > > >> - download dtrace.patch to somewhere, lets say /tmp, then > > > >> # cd /usr/src/sys <-- sys subdirectory of a current head, > > > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? which you don't mind messing > > > >> up > > > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? doesn't have to be at > > > >> /usr/src/sys, > > > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? of course. > > > >> # patch -p1 < /tmp/dtrace.patch > > > >> > > > >> rick > > > >> > > > > > > > > What's the status on this patch? It would be nice to get > > > > dtrace/newnfs > > > > going for 9.0...it's not too late, right? > > > > > > > > I'll test the patch too BTW :) > > > > > > > > -Brandon > > > > > > > > > > So it looks like the patch was committed to HEAD, but the bits to > > > support the New NFS implementation were never flipped on -- is > > > that > > > for a good reason? > > > > > I know nothing about Dtrace, so if something needs to be > > changed/fixed, > > someone who understands these things will have to let me know. > > > > When I built a kernel with "options KDTRACE_HOOKS" and set > > dtraceall_load="YES" in /etc/rc.conf, > > it booted and > > # dtrace -l > > - seemed to find the stuff (it's called "dtnfscl", btw). > > > > Someone told me that's how you check it's loaded and that's all I > > know how to do w.r.t. dtrace. > > > > If you can test/debug it, that would be great, rick > > Actually, the problem is not with DTrace functioning, but with the > dtnfsclient.ko module: > > brandon@m6500:~$ sudo kldload dtnfsclient > kldload: can't load dtnfsclient: Exec format error > > brandon@m6500:~$ dmesg > ... > link_elf_obj: symbol nfsclient_accesscache_flush_done_id undefined > linker_load_file: Unsupported file type > ... > > Any hints on debugging undefined symbols? > dtnfsclient.ko is for the old nfs client. You either need to build a kernel with: options NFSCLIENT OR kldload nfsclient.ko However, if you want to test dtrace with the new (default for 9) NFS client, the dtrace module is dtnfscl.ko. rick ps: The above only applies to 9/-current, of course. > -Brandon > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
On Fri, Sep 02, 2011 at 08:25:05PM -0400, Rick Macklem wrote: > Brandon Gooch wrote: > > On Thu, Sep 1, 2011 at 8:09 PM, Brandon Gooch > > wrote: > > > On Fri, May 27, 2011 at 8:09 AM, Rick Macklem > > > wrote: > > >>> On Thu, 26 May 2011, Rick Macklem wrote: > > >>> ... > > >>> > ??http://people.freebsd.org/~rmacklem/dtrace.patch > > >>> > > > >>> Hmm. Is it just me? > > >>> Trying to test the patch I get: > > >>> > > >>> (fs)(root) patch -C < dtrace.patch > > >>> Hmm... I can't seem to find a patch in there anywhere. > > >>> > > >> Here's how I apply the patch. > > >> - download dtrace.patch to somewhere, lets say /tmp, then > > >> # cd /usr/src/sys <-- sys subdirectory of a current head, > > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? which you don't mind messing up > > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? doesn't have to be at /usr/src/sys, > > >> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? of course. > > >> # patch -p1 < /tmp/dtrace.patch > > >> > > >> rick > > >> > > > > > > What's the status on this patch? It would be nice to get > > > dtrace/newnfs > > > going for 9.0...it's not too late, right? > > > > > > I'll test the patch too BTW :) > > > > > > -Brandon > > > > > > > So it looks like the patch was committed to HEAD, but the bits to > > support the New NFS implementation were never flipped on -- is that > > for a good reason? > > > I know nothing about Dtrace, so if something needs to be changed/fixed, > someone who understands these things will have to let me know. > > When I built a kernel with "options KDTRACE_HOOKS" and set > dtraceall_load="YES" in /etc/rc.conf, > it booted and > # dtrace -l > - seemed to find the stuff (it's called "dtnfscl", btw). > > Someone told me that's how you check it's loaded and that's all I > know how to do w.r.t. dtrace. > > If you can test/debug it, that would be great, rick Actually, the problem is not with DTrace functioning, but with the dtnfsclient.ko module: brandon@m6500:~$ sudo kldload dtnfsclient kldload: can't load dtnfsclient: Exec format error brandon@m6500:~$ dmesg ... link_elf_obj: symbol nfsclient_accesscache_flush_done_id undefined linker_load_file: Unsupported file type ... Any hints on debugging undefined symbols? -Brandon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
Brandon Gooch wrote: > On Thu, Sep 1, 2011 at 8:09 PM, Brandon Gooch > wrote: > > On Fri, May 27, 2011 at 8:09 AM, Rick Macklem > > wrote: > >>> On Thu, 26 May 2011, Rick Macklem wrote: > >>> ... > >>> > http://people.freebsd.org/~rmacklem/dtrace.patch > >>> > > >>> Hmm. Is it just me? > >>> Trying to test the patch I get: > >>> > >>> (fs)(root) patch -C < dtrace.patch > >>> Hmm... I can't seem to find a patch in there anywhere. > >>> > >> Here's how I apply the patch. > >> - download dtrace.patch to somewhere, lets say /tmp, then > >> # cd /usr/src/sys <-- sys subdirectory of a current head, > >> which you don't mind messing up > >> doesn't have to be at /usr/src/sys, > >> of course. > >> # patch -p1 < /tmp/dtrace.patch > >> > >> rick > >> > > > > What's the status on this patch? It would be nice to get > > dtrace/newnfs > > going for 9.0...it's not too late, right? > > > > I'll test the patch too BTW :) > > > > -Brandon > > > > So it looks like the patch was committed to HEAD, but the bits to > support the New NFS implementation were never flipped on -- is that > for a good reason? > I know nothing about Dtrace, so if something needs to be changed/fixed, someone who understands these things will have to let me know. When I built a kernel with "options KDTRACE_HOOKS" and set dtraceall_load="YES" in /etc/rc.conf, it booted and # dtrace -l - seemed to find the stuff (it's called "dtnfscl", btw). Someone told me that's how you check it's loaded and that's all I know how to do w.r.t. dtrace. If you can test/debug it, that would be great, rick > -Brandon > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
On Thu, Sep 1, 2011 at 8:09 PM, Brandon Gooch wrote: > On Fri, May 27, 2011 at 8:09 AM, Rick Macklem wrote: >>> On Thu, 26 May 2011, Rick Macklem wrote: >>> ... >>> > http://people.freebsd.org/~rmacklem/dtrace.patch >>> > >>> Hmm. Is it just me? >>> Trying to test the patch I get: >>> >>> (fs)(root) patch -C < dtrace.patch >>> Hmm... I can't seem to find a patch in there anywhere. >>> >> Here's how I apply the patch. >> - download dtrace.patch to somewhere, lets say /tmp, then >> # cd /usr/src/sys <-- sys subdirectory of a current head, >> which you don't mind messing up >> doesn't have to be at /usr/src/sys, >> of course. >> # patch -p1 < /tmp/dtrace.patch >> >> rick >> > > What's the status on this patch? It would be nice to get dtrace/newnfs > going for 9.0...it's not too late, right? > > I'll test the patch too BTW :) > > -Brandon > So it looks like the patch was committed to HEAD, but the bits to support the New NFS implementation were never flipped on -- is that for a good reason? -Brandon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
On Fri, May 27, 2011 at 8:09 AM, Rick Macklem wrote: >> On Thu, 26 May 2011, Rick Macklem wrote: >> ... >> > http://people.freebsd.org/~rmacklem/dtrace.patch >> > >> Hmm. Is it just me? >> Trying to test the patch I get: >> >> (fs)(root) patch -C < dtrace.patch >> Hmm... I can't seem to find a patch in there anywhere. >> > Here's how I apply the patch. > - download dtrace.patch to somewhere, lets say /tmp, then > # cd /usr/src/sys <-- sys subdirectory of a current head, > which you don't mind messing up > doesn't have to be at /usr/src/sys, > of course. > # patch -p1 < /tmp/dtrace.patch > > rick > What's the status on this patch? It would be nice to get dtrace/newnfs going for 9.0...it's not too late, right? I'll test the patch too BTW :) -Brandon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
> On Thu, 26 May 2011, Rick Macklem wrote: > ... > > http://people.freebsd.org/~rmacklem/dtrace.patch > > > Hmm. Is it just me? > Trying to test the patch I get: > > (fs)(root) patch -C < dtrace.patch > Hmm... I can't seem to find a patch in there anywhere. > Here's how I apply the patch. - download dtrace.patch to somewhere, lets say /tmp, then # cd /usr/src/sys <-- sys subdirectory of a current head, which you don't mind messing up doesn't have to be at /usr/src/sys, of course. # patch -p1 < /tmp/dtrace.patch rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
On Thu, 26 May 2011, Rick Macklem wrote: ... http://people.freebsd.org/~rmacklem/dtrace.patch Hmm. Is it just me? Trying to test the patch I get: (fs)(root) patch -C < dtrace.patch Hmm... I can't seem to find a patch in there anywhere. Bye/2 --- Michael Reifenberger mich...@reifenberger.com http://www.Reifenberger.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
On Fri, 27 May 2011, Alexander Leidinger wrote: Date: Fri, 27 May 2011 10:43:58 +0200 From: Alexander Leidinger To: Michael Reifenberger Cc: Rick Macklem , FreeBSD-Current Subject: Re: newnfs user setup Quoting Michael Reifenberger (from Fri, 27 May 2011 10:02:09 +0200 (CEST)): - make buildworld WITH_CTF=1 && make buildkernel WITH_CTF=1 Do not build world with CTF, this will produce broken static executables. Ups. Thanks for reminding! Bye/2 --- Michael Reifenberger mich...@reifenberger.com http://www.Reifenberger.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
Quoting Michael Reifenberger (from Fri, 27 May 2011 10:02:09 +0200 (CEST)): - make buildworld WITH_CTF=1 && make buildkernel WITH_CTF=1 Do not build world with CTF, this will produce broken static executables. Bye, Alexander. -- Freedom is nothing else but the chance to do better. -- Camus http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
On Thu, 26 May 2011, Rick Macklem wrote: ... Alternately, if you could email me some simple instructions on how to test it, that would be appreciated as well. (I have never used DTrace, so I have no idea how to test it.) It is basically a clone of the other one, except for the NFSv4 stuff, so it "should" work about the same. The simplest way of a basic test should be: - Put into your kernel.conf: options KDTRACE_FRAME # could be for amd64 only options KDTRACE_HOOKS options DDB_CTF # could be optional - make buildworld WITH_CTF=1 && make buildkernel WITH_CTF=1 - Put into your loader.conf: dtraceall_load="YES" After reboot check: dtrace -l If you see lots of fbt and sdt (esp. the nfs ones) providers all should be prepared and fine. Bye/2 --- Michael Reifenberger mich...@reifenberger.com http://www.Reifenberger.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
> > One thing that initially forgot - what about lockd and statd? > Do I still need them with newnfs and NFSv3 to get fcntl/flock working? > And do those actually work? :-) > Yes, and they haven't changed so they work just like before, which means ymmv when using them. > I understand that with NFSv4 I don't need those anymore. > That is correct. NFSv4 has file locking built in. rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
> On Thu, 26 May 2011, Rick Macklem wrote: > > > Date: Thu, 26 May 2011 09:14:01 -0400 (EDT) > > From: Rick Macklem > > To: Andriy Gapon > > Cc: Rick Macklem , > > FreeBSD-Current > > Subject: Re: newnfs user setup > > > >> Rick, > >> > >> maybe I've just not looked hard enough, but I am a little bit > >> confused > >> about how > >> to setup properly newnfs server and client via rc.conf. > >> That is, I am not sure which exactly daemons I need and what > >> variables > >> to set. > >> > > I dunno if its matters here but it seems that the usage of DTrace > (esp. > dtnfsclient) forces the usage of oldnfs. > > Is it possible to use both oldnfs and newnfs kernel objects at once > or does the usage of newnfs prohibit the usage of dtrace? > I have a DTrace patch for the new NFS client. The current version, (which would apply to a -current kernel recently but if it won't patch now, I can easily fix it) is at: http://people.freebsd.org/~rmacklem/dtrace.patch I have been waiting for a review/test of it, but if you could test it, that would be greatly appreciated. Once built, the module is called dtnfscl. Alternately, if you could email me some simple instructions on how to test it, that would be appreciated as well. (I have never used DTrace, so I have no idea how to test it.) It is basically a clone of the other one, except for the NFSv4 stuff, so it "should" work about the same. If I don't get any review/testing done, I'll commit it "as is" before the code slush deadline. rick ps: I'll try applying the patch now and fix it if it needs changing, so if you download it from the above in a few hours, it should be ok. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
On Thu, 26 May 2011, Rick Macklem wrote: Date: Thu, 26 May 2011 09:14:01 -0400 (EDT) From: Rick Macklem To: Andriy Gapon Cc: Rick Macklem , FreeBSD-Current Subject: Re: newnfs user setup Rick, maybe I've just not looked hard enough, but I am a little bit confused about how to setup properly newnfs server and client via rc.conf. That is, I am not sure which exactly daemons I need and what variables to set. I dunno if its matters here but it seems that the usage of DTrace (esp. dtnfsclient) forces the usage of oldnfs. Is it possible to use both oldnfs and newnfs kernel objects at once or does the usage of newnfs prohibit the usage of dtrace? Bye/2 --- Michael Reifenberger mich...@reifenberger.com http://www.Reifenberger.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
on 26/05/2011 16:14 Rick Macklem said the following: > avg said the following: >> So I would appreciate an example here. >> > I don`t think any changes are necessary, although it would be nice if you > grabbed the new rc.d scripts and tested them. > One thing that initially forgot - what about lockd and statd? Do I still need them with newnfs and NFSv3 to get fcntl/flock working? And do those actually work? :-) I understand that with NFSv4 I don't need those anymore. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
First, thank you very much for all the help! on 26/05/2011 16:41 Rick Macklem said the following: > Btw, it would be nice to find out why it doesn't load. You might > try "kldload -v nfsserver.ko" and see what happens? (It loads for > me here.) Oh, it looks that I just don't compile/install this module (I have MODULES_OVERRIDE), so no problem here. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
> Well, for head/current, I don't think you'll need anything different > unless > you want to run NFSv4. If you want to force use of the old nfs server, > you > can do that with: > oldnfs_server_enable="YES" > > As for the client side, I have up to date scripts for /etc/rc.d in > http://people.freebsd.org/~rmacklem/rc.conf > - I am waiting for a review on those, before they go into head. > > > The reason I am asking is that I see some things than seems > > unexpected > > to me. > > For example, rc.d/nfsserver tries to load nfsserver.ko, but that > > fails > > in my > > environment: > > root: /etc/rc: WARNING: Unable to load kernel module nfsserver > Hmm, I have no idea why the old server module won't load for you, but > if you want to run the new/default one, you don't need it anyhow. > (If you replace /etc/rc.d/nfsd with the one in ~rmacklem/rc.conf you > should delete /etc/rc.d/nfsserver. All it does is make the old nfs > server module load and my modified /etc/rc.d/nfsd does that, as > required.) > Btw, it would be nice to find out why it doesn't load. You might try "kldload -v nfsserver.ko" and see what happens? (It loads for me here.) > > And these modules come built into my kernel: > > $ kldstat -v | fgrep nfs > > 171 nfssvc > > 126 nfsd > > 123 nfscommon > > 172 nfslockd > > 124 nfs > > 130 unionfs > > 125 nfscl > > 170 nfslock > > > So you have the new client (nfscl) and new server (nfsd) already > loaded > and should be good to go. > > > Also, I see that rc.d/nfsclient has > > required_modules="nfsclient:oldnfs" > > which is also a little bit surprising. > > > This would just force loading of the old client. Harmless, but > unnecessary > unless you are using it. > This is because the rc.d scripts haven`t been updated for the client > yet. > (See above w.r.t. ones for review. The 3 that change are > mountcritremote, > nfsclient, plus a one line change to rc.conf in defaults.) > However, I think everything should work for your case. > > > So I would appreciate an example here. > > > I don`t think any changes are necessary, although it would be nice if > you > grabbed the new rc.d scripts and tested them. > Btw, you'll find two versions of the mountcritremote patch. One, called mountcritremote.diff2 is the minimal 1 line change needed to fix it. The other, called mountcritremote.diff, takes out all the nfs specific cruft that doesn't seem to be needed anymore, at least for the testing I've done. (If I can't get this well reviewed, I'll go with the 1 line change for head for now.) > > Also, for my future tests, I would like to get some pointers on > > getting started > > with NFSv4 in FreeBSD. > > > For the NFSv4 client, you need to: > nfsuserd_enable=``YES`` > Oh, and the mount command looks like: # mount -t nfs -o nfsv4 server:/path /mntpath > for the server > nfsv4_server_enable=``YES`` > nfs_server_enable=``YES`` > - you`ll also need to add a ``V4: ...`` line to your exports file. See > man exports or man nfsv4 > > rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: newnfs user setup
> Rick, > > maybe I've just not looked hard enough, but I am a little bit confused > about how > to setup properly newnfs server and client via rc.conf. > That is, I am not sure which exactly daemons I need and what variables > to set. > Well, for head/current, I don't think you'll need anything different unless you want to run NFSv4. If you want to force use of the old nfs server, you can do that with: oldnfs_server_enable="YES" As for the client side, I have up to date scripts for /etc/rc.d in http://people.freebsd.org/~rmacklem/rc.conf - I am waiting for a review on those, before they go into head. > The reason I am asking is that I see some things than seems unexpected > to me. > For example, rc.d/nfsserver tries to load nfsserver.ko, but that fails > in my > environment: > root: /etc/rc: WARNING: Unable to load kernel module nfsserver Hmm, I have no idea why the old server module won't load for you, but if you want to run the new/default one, you don't need it anyhow. (If you replace /etc/rc.d/nfsd with the one in ~rmacklem/rc.conf you should delete /etc/rc.d/nfsserver. All it does is make the old nfs server module load and my modified /etc/rc.d/nfsd does that, as required.) > And these modules come built into my kernel: > $ kldstat -v | fgrep nfs > 171 nfssvc > 126 nfsd > 123 nfscommon > 172 nfslockd > 124 nfs > 130 unionfs > 125 nfscl > 170 nfslock > So you have the new client (nfscl) and new server (nfsd) already loaded and should be good to go. > Also, I see that rc.d/nfsclient has > required_modules="nfsclient:oldnfs" > which is also a little bit surprising. > This would just force loading of the old client. Harmless, but unnecessary unless you are using it. This is because the rc.d scripts haven`t been updated for the client yet. (See above w.r.t. ones for review. The 3 that change are mountcritremote, nfsclient, plus a one line change to rc.conf in defaults.) However, I think everything should work for your case. > So I would appreciate an example here. > I don`t think any changes are necessary, although it would be nice if you grabbed the new rc.d scripts and tested them. > Also, for my future tests, I would like to get some pointers on > getting started > with NFSv4 in FreeBSD. > For the NFSv4 client, you need to: nfsuserd_enable=``YES`` for the server nfsv4_server_enable=``YES`` nfs_server_enable=``YES`` - you`ll also need to add a ``V4: ...`` line to your exports file. See man exports or man nfsv4 rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
newnfs user setup
Rick, maybe I've just not looked hard enough, but I am a little bit confused about how to setup properly newnfs server and client via rc.conf. That is, I am not sure which exactly daemons I need and what variables to set. The reason I am asking is that I see some things than seems unexpected to me. For example, rc.d/nfsserver tries to load nfsserver.ko, but that fails in my environment: root: /etc/rc: WARNING: Unable to load kernel module nfsserver And these modules come built into my kernel: $ kldstat -v | fgrep nfs 171 nfssvc 126 nfsd 123 nfscommon 172 nfslockd 124 nfs 130 unionfs 125 nfscl 170 nfslock Also, I see that rc.d/nfsclient has required_modules="nfsclient:oldnfs" which is also a little bit surprising. So I would appreciate an example here. Also, for my future tests, I would like to get some pointers on getting started with NFSv4 in FreeBSD. Thanks! -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
