[2359] in SIPB-AFS-requests
Kathleen_Rizzuti@transarc.com: vos release problems
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Tue May 14 18:09:29 1996
From: Jonathon Weiss <jweiss@MIT.EDU>
To: ops@MIT.EDU, afsdev@MIT.EDU, sipb-afsreq@MIT.EDU
Date: Tue, 14 May 1996 18:05:54 EDT
------- Forwarded Message
Message-Id: <QlaBBNeSMUgTJ1w2N=@transarc.com>
Date: Tue, 14 May 1996 14:39:21 -0400 (EDT)
From: Kathleen_Rizzuti@transarc.com
To: AFS_Contacts@transarc.com
Subject: vos release problems
Reply-To: <afshelp+@transarc.com>
AFS Contacts --
Recently, we have found two unusual problems with the AFS 3.4 version
of "vos release". While only a handful of customers have reported
these problems, we wanted to notify all AFS customers, since the
symptoms associated with these problems are somewhat misleading.
Empty or Partial RO (Base 4.39)
- -------------------------------
This situation arises when the administrator uses "vos addsite" to
define a new RO site for a volume that already has at least one RO
site, and then issues "vos release". While the "vos release" does not
report errors, the release itself is unexpectedly quick. When clients
access the newly created RO, they find that they can "cd" to its mount
point and list its contents, but get "file not found" errors when they
try to access actual file data. This is because the new volume is
either empty or only a partial copy of the RW.
A workaround is to issue "vos release -f", forcing the volserver to
distribute a new copy of the RW to all RO sites.
"Connection timed out" (Base 4.30 and higher)
- ---------------------------------------------
Under certain circumstances where a RO volume is being accessed
heavily during a "vos release", clients accessing the RO volume could
experience "Connection timed out" errors. These errors could cause
client applications to fail. As soon as the release completes, the
clients once again are able to access their data. This problem is
more likely to be seen when there are either 2 or 3 replicas.
A possible workaround is to make sure that you have at least 4
replicas on heavily accessed volumes.
Transarc and selected customers are currently testing fixes for both
problems. As soon as our testing is complete, we will release patched
binaries to all customers in a new AFS 3.4a patches release. At that
time, another announcement will be sent to all site contacts
announcing the availability of the release.
In the meantime, if you are currently experiencing any of the above
mentioned problems, please contact Product Support via the hotline at
(412) 281-5852 or via email at afshelp@transarc.com.
Kathy Rizzuti
Area Manager, File Systems Support
Transarc Corporation
------- End of Forwarded Message
