Re: Testing needed - HAMMER PFS exports via NFS

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Is null mount meant to be a permanent solution for PFS nfs export?

    Yes.

:Testing:
:Both nfs server and client running dfly HEAD;
:3 PFSs nfs exported: /usr/src, /usr/obj and my home dir;
:did some world/kernel building with above nfs mounts.
:
:Errors:
: - on nfs client (GENERIC) - buildkernel did abort
:Sep 22 13:15:01 boy kernel: nfs_getpages: error 13
:Sep 22 13:15:01 boy kernel: vm_fault: pager read error, pid 75644 (ld)
:Sep 22 13:15:01 boy kernel: pid 75644 (ld), uid 0: exited on signal 11

    Error 13?  That's 'permission denied'.  It sounds like cockpit trouble.
    Is the server exporting the filesystem with -maproot=root: ?  If not
    then there could be issues because the getpages/putpages code might
    run with root creds and if you do not export with -maproot=root: the
    root creds won't match.

    There might be nfs mount options to force the creds, I'm not sure.  The
    best solution is typically to export on the server with '-maproot=root:'.

: - on SMP nfs server (from 21:19 also server) - didn=B4t notice any ill eff=
:ect
:Sep 22 18:24:04 boy kernel: spin_lock: 0xc6087fdc, indefinite wait!
:Sep 22 19:08:10 boy kernel: spin_lock: 0xc6087fdc, indefinite wait!
:Sep 22 21:37:18 boy kernel: spin_lock: 0xc6087fdc, indefinite wait!
:Sep 22 22:03:27 boy kernel: spin_lock: 0xc6087fdc, indefinite wait!
:
: -thomas

    Hmm.  Well, since they didn't deadlock the kernel I'm guessing it
    was just a very long-held spin lock that eventually cleared.  We
    should try to track it down if possible, though.  Don't worry about
    it for now.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>