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: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Neulinger, Nathan > Sent: Friday, March 22, 2002 8:51 AM > To: [EMAIL PROTECTED] > Subject: [OpenAFS-devel] reproducible afsd/libafs lockup > > > 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 > cm lockup > by doing this in a high level directory in my cell. (i.e. a dir with > alot of stuff under it). > > find . -follow -type f -print | xargs -P 8 -n 30 wc > > 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. > > -- Nathan > > ------------------------------------------------------------ > Nathan Neulinger EMail: [EMAIL PROTECTED] > University of Missouri - Rolla Phone: (573) 341-4841 > Computing Services Fax: (573) 341-4216 > _______________________________________________ > OpenAFS-devel mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel > _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
