Date: Thu, 6 Mar 2008 20:49:16 -0600 From: Alec Kloss <alec-dated-1205290157.d7dd21@SetFilePointer.com> To: Alec Kloss <alec-keyword-freebsd.befd64@SetFilePointer.com> Cc: Alec Kloss <alec-keyword-freebsd.org.a6e2e4@SetFilePointer.com>, Rasmus Kaj <kaj@kth.se>, Garance A Drosehn <gad@FreeBSD.org>, afs@FreeBSD.org, Robert Watson <rwatson@FreeBSD.org>, Tomas Olsson <tol@stacken.kth.se>, arla-drinkers@stacken.kth.se Subject: Re: arla-devel port for FreeBSD (was: Patches to get Arla running on FreeBSD 8-CURRENT) Message-ID: <20080307024916.GC1911@hamlet.SetFilePointer.com> In-Reply-To: <20080303045554.GC8919@hamlet.SetFilePointer.com> References: <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <p0624081bc3e936674ece@[128.113.24.47]> <20080226061140.GI28956@hamlet.SetFilePointer.com> <20080301210055.GA8919@hamlet.SetFilePointer.com> <20080302161258.L21146@fledge.watson.org> <1204477663.4180.36.camel@hippo.t.nxs.se> <20080303045554.GC8919@hamlet.SetFilePointer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--qtZFehHsKgwS5rPz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. =20 Anyway, any hints about debugging arla would be welcome. Thanks much. --=20 Alec Kloss alec@SetFilePointer.com IM: angryspamhater@yahoo.com PGP key at http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xA241980E "No Bunny!" -- Simon, from Frisky Dingo --qtZFehHsKgwS5rPz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFH0K0s2s33paJBmA4RAnyjAJ0dEuFI7fh2+vzfvv4ypShw3K9QvgCePMyG PiDR9xyk1gl2nWFJls4w0Zc= =dKYA -----END PGP SIGNATURE----- --qtZFehHsKgwS5rPz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080307024916.GC1911>