[OpenAFS-devel] reproducible afsd/libafs lockup

[Neulinger, Nathan]

Interesting... I grabbed fsstress from kolya's web page and started
running it on this station. The instant I start running it against an
afs directory that client loses contact with the server that the test
afs dir is located on. Running fs checks regains connection. And that is
with a -p 1 test. Haven't even tried the -p # for larger #.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Neulinger, Nathan=20
> Sent: Friday, March 22, 2002 8:51 AM
> To: openafs-devel@openafs.org
> Subject: [OpenAFS-devel] reproducible afsd/libafs lockup
>=20
>=20
> Have not dug into this much yet, but with recent (and maybe old, not
> sure since I don't have a machine I can hose at the moment that is
> running old code) builds, I can trigger a real quick complete=20
> cm lockup
> by doing this in a high level directory in my cell. (i.e. a dir with
> alot of stuff under it).
>=20
> find . -follow -type f -print | xargs -P 8 -n 30 wc
>=20
> This one is a different symptom and situation from the other problem
> I've been talking about. In that problem, you can still talk to the
> cache manager with cmdebug and fs. With this one, the cm is totally
> non-responsive.=20
>=20
> -- Nathan
>=20
> ------------------------------------------------------------
> Nathan Neulinger                       EMail:  nneul@umr.edu
> University of Missouri - Rolla         Phone: (573) 341-4841
> Computing Services                       Fax: (573) 341-4216
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20