For the record, the *incorrect* official documentation section
about loading the kernel module under Solaris:
BEGIN QUOTE
If the machine is running Solaris 2.6 or the 32-bit version of Solaris
7, its kernel supports NFS server functionality, and the nfsd process is
running:
# cp -p modload/libafs.o /kernel/fs/afs
If the machine is running Solaris 2.6 or the 32-bit version of Solaris
7, and its kernel does not support NFS server functionality or the nfsd
process is not running:
# cp -p modload/libafs.nonfs.o /kernel/fs/afs
If the machine is running the 64-bit version of Solaris 7, its kernel
supports NFS server functionality, and the nfsd process is running:
# cp -p modload/libafs64.o /kernel/fs/sparcv9/afs
If the machine is running the 64-bit version of Solaris 7, and its
kernel does not support NFS server functionality or the nfsd process is
not running:
# cp -p modload/libafs64.nonfs.o /kernel/fs/sparcv9/afs
END QUOTE
Jeff Blaine wrote:
No, the NFS translator is not in use. I was under the
impression that the 'nonfs' module is only to be used
when the host in question is NOT acting as an NFS server.
This host is acting as an NFS server and AFS client.
When the NFS share(s) gets tickled in various ways, the
box croaks.
mdb '::stack' output -- does this help, Derrick?
is_afs_fh3+8(0, 6000ee4a554, 0, a, 0, 30001213c40)
nfs3_to_afs_call+0x1b4(3, 2a101c9f500, 2a101c9f168, 2a101c9f160,
2a101c9f500, 0)
afs_nfs3_dispatcher+0xa8(0, 3, 2a101c9f500, 2a101c9f298, 2a101c9f698,
81530a02)
afs_nfs3_lookup+0x34(2a101c9f500, 2a101c9f398, 60001002218,
2a101c9f698, 6000ee4a4e0, 1)
common_dispatch+0x564(2a101c9f698, 600132ee380, 0, 6000e3e7900,
705721b8, 0)
svc_getreq+0x1c8(600132ee380, 600135c2000, 6000875f1d0, 6000102de00,
704eae60, 6000875f040)
svc_run+0x198(6000ec4a048, 0, 0, 0, 6000ec4a080, 1)
nfssys+0x1c4(c, 1, 7b285800, c, 1f8, 30)
syscall_trap32+0xcc(e, ff071f9c, 0, 0, 0, 1)
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
