CIFS mount causing NFS errors

[john leavens_1]

I am running HPUX 11i V1.6 and have cifsclient running. I am mounting a share named /mnt/backup on a WIN2K host called BLAH. /etc/fstab entry for this looks like:

BLAH:backup /mnt/backup cifs defaults 0 0

I can mount and do a cifslogin just fine, but if the share is mounted but not logged into bdf gives the following error.

NFS access failed for server BLAH: RPC: Remote system error

I thought I had all NFS turned off since, I have all NFS daemons and automounter turned off in /etc/rc.config.d/nfsconf


A ps shows a process named nfskd that I have tried to kill (kill -9 ) but it will not die.

Any ideas on:

1) Why nfs would running?
2) Are NFS and cifsclient some how dependent?

Thanks,
JohnL

[Sanjiv Sharma_1]

Hi John,

Please check this links:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1079220269846+28353475&threadId=117733
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=59487

[The Real MD]

NFS exports go into /etc/exports
CIFS shares go in to smb.conf
or use http://:901 to use the web based confuiguration tool.


NFS and CIFS are completely independent you can have one or the other working, both or none there is no interdependancy.


Regards

Martin.

[Alzhy]

John,

I have not gotten a concrete explanation from HP about why CIFSclient timeouts appear as NFS errors but the fix that we got was to upgrade to whatever version was release after July 2003. A....09 something.

For everyone's information, HP based its CIFS/9000 Client product from the Sharity Product (http://www.obdev.at/products/sharity/)

I was one of those who worked with HP to check/test on the refinements they had implemented on the CIFS/9000 Client product.

[Mark Grant]

NFS and CIFS can happily coexist and neither onw knows about the other one. They do not bother each other. However, your error message is a bother. To make sure, cd to /sbin/init.d and do

nfs.client stop
nfs.server stop
nfs.core stop

That should pretty much ensure NFS is stopped. However, I be surprised if it was the root of your problem.