[OpenAFS-devel] Re: progress... sortof...

[Neulinger, Nathan]

It's not all the time... but certain user written code definately
triggers the problem, and once it's hit once, it takes the machine down.
I hae one set of user code (unfortunately not very minimal) that seems
to trigger it very reliably on some of the boxes I have.=20

I do not believe that clearing the AFS cache has had any effect.

Shouldn't that be -EIO?

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216
=20

>=20
> So actually I think the right thing to do is:
>=20
> 	if (code =3D=3D 0) {
> 		code =3D EIO;
> 		break;
> 	}
>=20
> because otherwise, this function will return 0, and the caller
> (afs_UFSRead, afs_UFSWrite) will assume that it successfully read all
> the data it wanted to read.
>=20
> The question is, what's going on with your machine that's=20
> causing it to
> do short reads all the time?  Is your cache corrupted, or=20
> running out of
> space?  Can you put debug statements to see what cache file is causing
> the problem, and which vnode it corresponds to?  Does=20
> clearing your AFS
> cache fix the problem?
>=20
> -- kolya
>=20
>=20
>=20