[4017] in SIPB bug reports
Re: Fun corruption in the sipb locker
daemon@ATHENA.MIT.EDU (mhpower@athena.mit.edu)
Fri Aug 6 17:50:13 1993
From: mhpower@athena.mit.edu
To: ckclark@athena.mit.edu
Cc: sipb-afsreq@athena.mit.edu, bug-sipb@athena.mit.edu
In-Reply-To: "[4014] in SIPB bug reports", "[1100] in SIPB-AFS-requests"
Date: Fri, 06 Aug 93 17:49:34 EDT
> ... I tried to salvage the volume, but the salvager
>dumped core. (See [0477] in AFS_bugs.) The file exists in the
>read-write volume, so when it is released in a couple of hours, the
>particular case you've mentioned might go away.
Actually, it didn't go away.... On the dialup client al-burro, for
example, the same "gz.1: No such file or directory" error that cfields
reported is still occurring. Other clients, e.g., the dialup
primavera, don't have the problem.
As I mentioned in [1096] in sipb-afs, vos release doesn't seem to
help, even though the problem affects only RO access, not RW.
Matt