[OpenAFS-devel] reproducible afsd/libafs lockup

[Neulinger, Nathan]

Ok. I narrowed it down. Attempting to make a symlink with target length
> 1024 will immediately cause client to lose contact with file server on
linux.=20

This appears to be linux specific, and is not specific to recent client
builds, even happening on an old 2.2.x build I have.

-- 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 9:27 AM
> To: openafs-devel@openafs.org
> Subject: RE: [OpenAFS-devel] reproducible afsd/libafs lockup
>=20
>=20
> Appears this test causes it:
>=20
> troot-srvtst07(132)> fs checks ; ./fsstress -v -n 8 -p 1 -d
> /umr/u/nneul/fsstress/
> All servers are running.
> seed =3D 1016547366
> 0/0: dwrite - no filename
> 0/1: chown . 7536 0
> 0/2: creat f0 x:0 0 0
> 0/3: symlink l1 0
> 0/4: fdatasync - no filename
> 0/5: symlink l2 110
> 0/6: truncate - no filename
> 0/7: creat f3 x:0 110 0
>=20
> I'm trying to track down a more specific trigger.
>=20
> -- Nathan
>=20
> ------------------------------------------------------------
> Nathan Neulinger                       EMail:  nneul@umr.edu
> University of Missouri - Rolla         Phone: (573) 341-4841
> Computing Services                       Fax: (573) 341-4216
>=20
>=20
> > -----Original Message-----
> > From: Neulinger, Nathan=20
> > Sent: Friday, March 22, 2002 9:15 AM
> > To: openafs-devel@openafs.org
> > Subject: RE: [OpenAFS-devel] reproducible afsd/libafs lockup
> >=20
> >=20
> > Interesting... I grabbed fsstress from kolya's web page and started
> > running it on this station. The instant I start running it=20
> against an
> > afs directory that client loses contact with the server=20
> that the test
> > afs dir is located on. Running fs checks regains connection.=20
> > And that is
> > with a -p 1 test. Haven't even tried the -p # for larger #.
> >=20
> > -- Nathan
> >=20
> > ------------------------------------------------------------
> > Nathan Neulinger                       EMail:  nneul@umr.edu
> > University of Missouri - Rolla         Phone: (573) 341-4841
> > Computing Services                       Fax: (573) 341-4216
> >=20
> >=20
> > > -----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=20
> 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.=20
> 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=20
> other problem
> > > I've been talking about. In that problem, you can still=20
> talk to the
> > > cache manager with cmdebug and fs. With this one, the cm=20
> 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
> > _______________________________________________
> > OpenAFS-devel mailing list
> > OpenAFS-devel@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-devel
> >=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20