Re: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT)
Alec Kloss <[email protected]> Thu, 6 Mar 2008 20:49:16 -0600
| Newsgroups | gmane.os.freebsd.devel.afs,gmane.comp.file-systems.arla.general |
|---|---|
| Message-ID | <[email protected]> |
So I've been kicking arla around a bunch. Unfortunately, but probably not surprisingly, I've found that the 20080301 snapshot seems to lack some of the stability of 0.43 running on 5.5. Of course, it'll actually play video and such without caching the whole file first, which is nice. :) Anyway, Tomas, or others, do you have any hints for me about how best to start diagnosing and maybe fixing issues? The most repeatable way I've found to get bad behavior is to rsync -a /usr/src and /usr/obj into AFS. After 30 seconds or so of this, I'll start getting messages like these: lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock lockmgr: thread 0xc6970840 unlocking unheld lock on the console. Eventually, rsync will block and generally things will decay. Overnight, I'm going to script the console while attempting this with nnpfsdeb almost-all set. This is, of course, a lot slower than arla normally runs, but I'm hoping someone may be able to see the source of the trouble. I'll post the console somewhere tomorrow. Anyway, any hints about debugging arla would be welcome. Thanks much. -- Alec Kloss [email protected] IM: [email protected] PGP key at http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA241980E "No Bunny!" -- Simon, from Frisky Dingo
signature.asc
(application/pgp-signature, 187 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFH0K0s2s33paJBmA4RAnyjAJ0dEuFI7fh2+vzfvv4ypShw3K9QvgCePMyG PiDR9xyk1gl2nWFJls4w0Zc= =dKYA -----END PGP SIGNATURE-----