search for: nfssrv

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 4af930f29a665f04c4cf91ef1fbc049fb427a304 Log message: 6417056 nfssrv should use doors/xdr as its IPC mech to mountd(1m) Files: create: deleted_files/usr/src/uts/common/rpcsvc/nfsauth_prot.x create: usr/src/cmd/fs.d/nfs/mountd/nfsauth_xdr.c create: usr/src/uts/common/fs/nfs/nfs_auth_xdr.c create: usr/src/uts/common/nfs/auth.h delete: usr/src/uts/common/rpcsvc/n...

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 7413fc53072f4145c1b3ac0e2169234084b4c6ab Log message: 6417056 nfssrv should use doors/xdr as its IPC mech to mountd(1m) (fix unref) Files: create: deleted_files/usr/src/cmd/fs.d/nfs/mountd/svc_local.c delete: usr/src/cmd/fs.d/nfs/mountd/svc_local.c

We're running Samba 2.2.2 over an NT network. Our clients use Win95 (for the time being) and I wondered how we config Samba so they can map the shares using network neighborhood. We can map fine through MS-DOS, but when I try, for example, to map E drive to \\nfssrv\ads share via network neighborhood (where we ARE able to see the shares), it says E: is already connected to . Do you want to connect E: to \\nfssrv\ads instead? I respond 'yes' and it just keeps giving me the same message. What are we doing wrong? I was told as long as our shares a...

I want to list/use the nfs probes but I get the error "dtrace: failed to match nfs*:::: No probe matches description". Is there a way to enable nfs provider probes? My system is running snv_112 (bfu''ed from the gate archive) # dtrace -lP nfs* ID PROVIDER MODULE FUNCTION NAME dtrace: failed to match nfs*:::: No probe matches

...003e032550 ip:udp_wput+fe () ffffff003e0325c0 unix:putnext+21e () ffffff003e032600 rpcmod:rpcmodwput+9b () ffffff003e032620 rpcmod:rmm_wput+1e () ffffff003e032690 unix:put+1aa () ffffff003e0326f0 rpcmod:svc_clts_ksend+1da () ffffff003e032770 rpcmod:svc_sendreply+56 () ffffff003e032a70 nfssrv:common_dispatch+6b2 () ffffff003e032a90 nfssrv:rfs_dispatch+2d () ffffff003e032b70 rpcmod:svc_getreq+19c () ffffff003e032bd0 rpcmod:svc_run+16b () ffffff003e032c00 rpcmod:svc_do_run+81 () ffffff003e032ec0 nfs:nfssys+765 () ffffff003e032f10 unix:brand_sys_syscall32+1cd () syncing file...

We recently had a strange NFS performance anomaly between a V880 running snv_124 and two NetApp filers. To investigate, a DTrace NFSv4 (and eventually NFSv3) client provider would been extremely helpful. Unfortunately, all I could find were a request for code review of a v3 client provider and another request for help developing a v4 provider. Nothing seems to have come from those initiatives,

FYI, I posted a blog a few days ago about a DTrace provider for NFS that is currently in development: http://blogs.sun.com/roller/page/samf?entry=a_dtrace_provider_for_nfs Let''s discuss any questions, comments, etc. here. I also advertised this on nfs-discuss at opensolaris.org. Naturally, I would expect the discussion here to be more on the specifics of DTrace, and the

Hi Folks, I''ve got a 3.9 Tb zpool, and it is casing kernel panics on my Solaris 10 280r (SPARC) server. The message I get on panic is this: panic[cpu1]/thread=2a100a95cc0: zfs: freeing free segment (offset=423713792 size=1024) This seems to come about when the zpool is being used or being scrubbed - about twice a day at the moment. After the reboot, the scrub seems to have