From owner-freebsd-stable@FreeBSD.ORG Thu May 25 15:31:11 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7DF316A4AC for ; Thu, 25 May 2006 15:31:11 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B62043D46 for ; Thu, 25 May 2006 15:31:10 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 3047 invoked from network); 26 May 2006 01:31:09 +1000 Received: from 203-214-153-204.perm.iinet.net.au (HELO localhost) (203.214.153.204) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 May 2006 01:31:09 +1000 Date: Fri, 26 May 2006 01:31:05 +1000 From: Norberto Meijome To: stable@freebsd.org Message-ID: <20060526013105.22ee47ad@localhost> In-Reply-To: <20060524020116.GB54710@xor.obsecurity.org> References: <20060524115659.7895006a@localhost> <20060524020116.GB54710@xor.obsecurity.org> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: GELI issues ? (Re: Increase in panics under 6.1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 15:31:15 -0000 On Tue, 23 May 2006 22:01:16 -0400 Kris Kennaway wrote: > So what is the traceback? > > See the developers handbook for more information. doh! yes, i'll get onto this as soon as I can. Interestingly enough , i had some nasty issues todays on same laptop. I had 2 x 6 GB GELI vnodes, running mtree -K md5digest to compare contents. Disk IO was high as expected...but then it just died down (but the mtree hadnt finished). (swap is also GELI) Any subsequent process trying to access the encrypted mount points simply stalled for as long as I cared to wait (10 minutes). The processes even stalled a shutdown -r. On restart, I repeated and had the same problem with only one of the encrpyed vnodes. Had to restart again - then I got the following msgs (which seem to have blocked the bg fsck) (apologies about wrapping): May 25 16:25:51 ayiin kernel: fsync: giving up on dirty May 25 16:25:51 ayiin kernel: 0xc4fe7aa0: tag devfs, type VCHR May 25 16:25:51 ayiin kernel: usecount 1, writecount 0, refcount 628 mountedhere 0xc4da5500 May 25 16:25:51 ayiin kernel: flags () May 25 16:25:51 ayiin kernel: v_object 0xc1025738 ref 0 pages 2499 May 25 16:25:51 ayiin kernel: lock type devfs: EXCL (count 1) by thread 0xc5296300 (pid 778) May 25 16:25:51 ayiin kernel: dev ad0s1f May 25 16:25:51 ayiin kernel: fsync: giving up on dirty May 25 16:25:51 ayiin kernel: 0xc4fe7aa0: tag devfs, type VCHR May 25 16:25:51 ayiin kernel: usecount 1, writecount 0, refcount 628 mountedhere 0xc4da5500 May 25 16:25:51 ayiin kernel: flags () May 25 16:25:51 ayiin kernel: v_object 0xc1025738 ref 0 pages 2499 May 25 16:25:51 ayiin kernel: lock type devfs: EXCL (count 1) by thread 0xc5296300 (pid 778) May 25 16:25:51 ayiin kernel: dev ad0s1f manual fsck fixed other issues. What was this all about? I couldnt waste any more time, so I booted 6.1-RELEASE , went to fixit, restored source and kernel from the CD, rebooted, rebuilt world... and everything is just fine now. I still have the older kernel (but not world) if it's useful. If anyone has any idea of what could have caused all these issues, i'd love to hear :) otherwise...i'll put it to a bad week compounded with Murphy's laws... cheers, Beto