[OpenAFS-devel] Windows Broken Pipes

[Lantzer, Ryan]

There have been more instances of this problem at our site, and we were
able to produce a trace dump that seems to have produced some usefull
output. I believe that a RO volume with 3 replicas was released just
before or just as the problem started occurring on this system. A couple
of seconds after the client received a cm_RevokeVolumeCallback() for the
volume in question, cm_GetCallback() was called and it looks like it was
trying to fetch the status of something within that volume. It looks
like the call to RXAFS_FetchStatus() failed two times with VOFFLINE
against two of the RO servers. But on the third try cm_ConnByMServers()
failed with CM_ERROR_NOSUCHVOLUME, making it look like it didn't even
try the third server. After receiving CM_ERROR_NOSUCHVOLUME, the
cm_GetCallback() function decides that the operation has failed and
exits. It looks like once cm_ConnByMServers() returns
CM_ERROR_NOSUCHVOLUME, there is no way for cm_Conn() to connect to that
volume again except after running 'fs checkv' to invalidate the volume
cache entry, and force it to be reloaded from the VLDB.

I found that once this problem had occurred, trying to flush the volume
in question using the Explorer interface resulted in the following error
message:

afs_shl_ext

Error flushing volume for S:\: Broken pipe

I'm still trying to find a way to reproduce this problem so that I can
perform additional tests to find out more about it.

In the mean time, does anyone know why CM_ERROR_NOSUCHVOLUME would be
returned for an offline volume? If there is a reason, shouldn't the
volume become available again after it comes back online?

Ryan Lantzer

-----Original Message-----
From: James Peterson  james@abrakus.com
Sent: Thu, 6 Mar 2003 09:14:43 -0800
To: 'openafs-devel@openafs.org'
Subject: [OpenAFS-devel] Windows Broken Pipes


Ryan I have seen something similar on my XP system.  The drive is not
labeled and is not accessible.  It has happened with "subst" drives
without
AFS running and AFS drives.  I was going to try and remove something
about
the drive definition from the registry and reboot.  I suspect its XP,
DOS
and I have been just living with it.  Lets stay in touch about this.

James
"Integrity is the Base of Excellence"

=09

-----Original Message-----
From: Lantzer, Ryan=20
Sent: Wednesday, March 05, 2003 10:25 AM
To: 'openafs-devel@openafs.org'
Subject: [OpenAFS-devel] Windows AFS client reports broken pipe when
trying to flush volumes that have become unavailable


At our site, we seem to have a large number of instances where one or
more (but not all) drives mapped to volumes on AFS appear to suddenly
become unavailable. The drives appear to be empty, and attempting to
flush the problematic volumes results in an error message indicating a
broken pipe. This problem does not seem to affect all drives mapped to
resources on AFS, since some drives mapped to different volumes continue
to work properly. Either rebooting or refreshing the volume ID/name map
appears to make things start working again. We are seeing the problem
under Windows XP Pro with OpenAFS 1.2.8 installed.

Has anyone else seen similar problems and/or know of a way to reproduce
this problem?

Ryan Lantzer