> I just wanted to know if typing mount<ret> showed a mount present on
> /net/us-titan.us.dev.bluearc.com/ARCHIVE
I found the output from cat /proc/mounts while "wide" (the machine with
the older kernel) had the problem. It alleges three mounts from that
server while the problem was happening:
us-titan.us.dev.bluearc.com:/CALLHOME
/net/us-titan.us.dev.bluearc.com/CALLHOME nfs
rw,nosuid,nodev,v3,rsize=32768,wsize=32768,hard,intr,lock,proto=tcp,addr
=us-
titan.us.dev.bluearc.com 0 0
us-titan.us.dev.bluearc.com:/ARCHIVE
/net/us-titan.us.dev.bluearc.com/ARCHIVE nfs
rw,nosuid,nodev,v3,rsize=32768,wsize=32768,hard,intr,lock,proto=tcp,addr
=us-ti
tan.us.dev.bluearc.com 0 0
us-titan.us.dev.bluearc.com:/Install
/net/us-titan.us.dev.bluearc.com/Install nfs
rw,nosuid,nodev,v3,rsize=32768,wsize=32768,hard,intr,lock,proto=tcp,addr
=us-ti
tan.us.dev.bluearc.com 0 0
("Install" is the right case but "CALLHOME" and "ARCHIVE" should both be
all lower-case.)
That matches my recollection of the symptom of duezer, though I'm having
a hard time proving it from the console logs.
-------------------------------------
Martin's Outlook, BlueArc Engineering
_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs
