hi -users, i'm running with two unstable boxes, one as an nfs client and the other as a server. when i try and connect from a client, it hangs indefinitely, and not only that, doesn't respond to backgrounding with ^Z or die with ^C. not surprisingly, it also does not respond to any signal delivered via kill. at some point later (maybe 5, 10 minutes), it looks like it finally recieves one of the 5000 kill signals i sent it, and dies. now the REALLY strange part... after it dies, the directory is mounted! does anyone know what's going on here? umount does not seem to have these problems afterwards, either. i had this problem about a year ago too, and thought it had to do with mismatched nfs kernel implementations, but now it seems like it's not. here's the relevant info: exports on the server: /usr/local/music 192.168.0.0/24(ro,sync) kernel settings on the server: CONFIG_NFS_FS=m CONFIG_NFS_V3=y # CONFIG_ROOT_NFS is not set CONFIG_NFSD=m CONFIG_NFSD_V3=y # CONFIG_NFSD_TCP is not set # CONFIG_NCPFS_NFS_NS is not set from the server's log: Mar 15 20:25:53 balthasar rpc.mountd: authenticated mount request from 192.168.0 .99:802 for /usr/local/music (/usr/local/music) kernel settings on the client: CONFIG_NFS_FS=m CONFIG_NFS_V3=y # CONFIG_ROOT_NFS is not set CONFIG_NFSD=m CONFIG_NFSD_V3=y # CONFIG_NFSD_TCP is not set # CONFIG_NCPFS_NFS_NS is not set any help would be greatly appreciated. sean
Attachment:
pgpD_W9pBssq7.pgp
Description: PGP signature