Russ Allbery <[EMAIL PROTECTED]> writes:
> Do all vos commands start failing on that file server? If so, you may
> have run into the same problem that we just ran into with the campus AFS
> servers. We needed to upgrade all of them with a patch to the vos
> server.
> You can get the patch at:
> /afs/ir.stanford.edu/dev/afs/openafs/PATCHES/openafs/vospatch
> I believe it's a bug fix that is already in 1.3.x and will be in the next
> stable (or already was in a stable version newer than what we happened to
> be running).
It occurs to me that that path is limited to Stanford users and this is a
one-line patch (plus then Derrick will know exactly what I'm talking
about). Here it is:
--- openafs-1.2.10a/src/viced/afsfileprocs.c.orig 2003-03-28 01:17:18.000000000
-0800
+++ openafs-1.2.10a/src/viced/afsfileprocs.c 2004-10-28 15:41:18.000000000 -0700
@@ -1064,6 +1064,7 @@
READ_LOCK, &rights, &anyrights)) {
tstatus = &OutStats->AFSBulkStats_val[i];
tstatus->errorCode = errorCode;
+ PutVolumePackage(parentwhentargetnotdir, targetptr, (Vnode *) 0, volptr);
parentwhentargetnotdir = (Vnode *) 0;
targetptr = (Vnode *) 0;
volptr = (Volume *) 0;
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
_______________________________________________
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info
