From owner-freebsd-afs@FreeBSD.ORG Sat Oct 2 06:54:55 2004 Return-Path: Delivered-To: freebsd-afs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B01A216A4CE for ; Sat, 2 Oct 2004 06:54:55 +0000 (GMT) Received: from s1.stradamotorsports.com (ip30.gte215.dsl-acs2.sea.iinet.com [209.20.215.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1213A43D2D for ; Sat, 2 Oct 2004 06:54:55 +0000 (GMT) (envelope-from jcw@highperformance.net) Received: from [192.168.1.16] ([192.168.1.16])i926sq8m032979; Fri, 1 Oct 2004 23:54:53 -0700 (PDT) (envelope-from jcw@highperformance.net) Date: Fri, 01 Oct 2004 23:54:54 -0700 From: "Jason C. Wells" To: "Jason C. Wells" , port-freebsd@openafs.org, freebsd-afs@freebsd.org Message-ID: In-Reply-To: <66F8A41B3F4164470D9446F2@[192.168.1.16]> References: <66F8A41B3F4164470D9446F2@[192.168.1.16]> X-Mailer: Mulberry/3.1.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, hits=-2.0 required=4.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: FreeBSD 5.2.1 Client Success! X-BeenThere: freebsd-afs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: The Andrew File System and FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2004 06:54:55 -0000 --On Friday, October 01, 2004 8:21 PM -0700 "Jason C. Wells" wrote: > I have been bugging folks for FreeBSD status reports for a while now. It > is my turn to make one. I have a working FreeBSD OpenAFS 1.3.71 client. > I plan to do some stress testing to see if it pukes. Yeah, it puked. :| Writing from and to AFS even simultaneously worked fine. Deleting was problematic. When running OpenAFS 1.3.71 on FreeBSD 5.2.1 an attempt to delete an AFS file results in: panic: lockmgr: locking against myself If anyone is working on the port anymore, I will be glad to work this issue in greater detail. I don't have the skill to hack a fix. Later, Jason C. Wells