[OpenAFS] Anyone else experiencing a cache bug in 64-bit OpenAFS for Windows 1.7.3200?

[Matt W. Benjamin]

Hi,

I run into "this" frequently on my Win 7 (64-bit) laptop.  I had a sense th=
e problem might
be related to changing networks and hibernation, but shamefully I haven't m=
ade any
real effort to root cause it.

In my random attempts to deal with it, I found that reboots (usually more t=
han
one) helped. It hadn't occurred to me to try flush the cache, I will rememb=
er
to try it next time I see this.

Thanks,

Matt

----- "Jeffrey Altman" <jaltman@your-file-system.com> wrote:

> On 11/25/2014 10:22 AM, Howard Jr, Russell A wrote:
> > Since October, I=E2=80=99ve been doing upgrades and new installs of the
> OpenAFS
> > Client using 1.7.3200.  We=E2=80=99ve recently encountered what appears=
 to
> be a
> > cache-related bug in this version but I haven=E2=80=99t found a way to
> reliably
> > reproduce it.  All clients are running Windows 8 x64 Enterprise as
> the OS.
> >=20
> > When the error occurs, it presents itself by the user seeing the
> > following message when trying to access any mapped AFS drives (=E2=80=
=9CM=E2=80=9D
> in
> > this case):
> >=20
> > M:\ is not accessible.
> >=20
> > The name of the file cannot be resolved by the system.
>=20
> This error can be generated from at least a thousand different
> causes.
> The Release Notes that ship with the client include debugging
> instructions that will help you identify the cause of the problem.
>=20
> > In order to restore AFS access on the machine, I had to stop the
> AFS
> > Client service, remove the cache file, and restart the service.
>=20
> Stopping the service will leave the kernel in an inconsistent state
> which can result in data corruption.  A reboot of the system should
> be
> performed at the earliest opportunity.
>=20
> There are many "fs" commands for manipulating the state of the cache
> manager
>=20
>   fs checkservers
>   fs checkvolumes
>   fs flush
>   fs flushvolume
>   fs flushall
>=20
> or examining the state
>=20
>   fs examine
>   fs memdump
>=20
> That should be used in preference to stopping the service.
>=20
> In particular, if you believe the problem is related to bad state
> information being stored in the AFSCache file then the "fs flushall"
> command would invalidate all of it without a service stop.

>=20
> This is the first report I have heard about it.

--=20
Matt Benjamin
CohortFS, LLC.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103

http://cohortfs.com

tel.  734-761-4689=20
fax.  734-769-8938=20
cel.  734-216-5309=20