Return-path: <alpha-osf-managers-relay_at_sws1.ctd.ornl.gov>
Received: from sws1.CTD.ORNL.GOV by SLUVCA.SLU.EDU (PMDF V5.0-4 #5070)
id <01HVTZI897Z48Y56IA_at_SLUVCA.SLU.EDU> for ALPHAOSF_at_SLUAVA.SLU.EDU; Fri,
29 Sep 1995 03:23:43 -0600 (CST)
Received: (from daemon_at_localhost) by sws1.CTD.ORNL.GOV (8.6.10/8.6.10)
id PAA09801 for aomaa; Mon, 25 Sep 1995 15:03:07 -0400
Received: from oaunx1.ctd.ornl.GOV (oaunx1.ctd.ornl.gov [128.219.128.17])
by sws1.CTD.ORNL.GOV (8.6.10/8.6.10) with ESMTP id PAA09789 for
<alpha-osf-managers_at_sws1.ctd.ornl.gov>; Mon, 25 Sep 1995 15:03:04 -0400
Received: from x.media.mit.edu by oaunx1.ctd.ornl.GOV (8.6.10/3.0-C)
id PAA29218; Mon, 25 Sep 1995 15:03:03 -0400
Received: from localhost by x.media.mit.edu; (5.65/1.1.8.2/23May94-0218PM)
id AA13401; Mon, 25 Sep 1995 15:02:15 -0400
Date: Mon, 25 Sep 1995 15:02:15 -0400
From: holtzman_at_mit.edu
Subject: mountd vs. ATM
Sender: alpha-osf-managers-relay_at_sws1.ctd.ornl.gov
To: alpha-osf-managers_at_ornl.gov
Cc: jwojcik_at_media.mit.edu, holtzman_at_mit.edu
Reply-to: holtzman_at_mit.edu
Reply-to: holtzman_at_mit.edu
Message-id: <9509251902.AA13401_at_x.media.mit.edu>
Content-transfer-encoding: 7BIT
Followup-to: poster
X-MTS: smtp
We're beginning the deployment of an ATM network, and it seems that
ATM-based mount requests are hanging our Digital Unix mountd.
Here is the setup:
client (Solaris 2.4) <-> ATM switch (FORE) <-> router (WellFleet)
^
|
/------ FDDI Concentrator<-----/
| |
| \->DEC 3000 AXP 800 running OSF/1 V3.2A
|
\->DEC 3000 AXP 600 running OSF/1 V2.1
When I tell the Sun to mount a filesystem on either the V2.1 or V3.2A
machine, the mountd on that machine wedges. It needs to be killed
and re-run for any mounts to work after that.
Has anybody seen anything like this, or know a solution?
-Henry
Received on Fri Sep 29 1995 - 12:35:49 NZST