From owner-freebsd-current@FreeBSD.ORG Tue Aug 2 00:14:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFE861065672 for ; Tue, 2 Aug 2011 00:14:32 +0000 (UTC) (envelope-from callumgibson@optusnet.com.au) Received: from fallbackmx07.syd.optusnet.com.au (fallbackmx07.syd.optusnet.com.au [211.29.132.9]) by mx1.freebsd.org (Postfix) with ESMTP id 04CCB8FC1C for ; Tue, 2 Aug 2011 00:14:31 +0000 (UTC) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by fallbackmx07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p71M8J64002326 for ; Tue, 2 Aug 2011 08:08:19 +1000 Received: from omma.gibson.athome (c122-106-15-156.rivrw1.nsw.optusnet.com.au [122.106.15.156]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with SMTP id p71M8F33030348 for ; Tue, 2 Aug 2011 08:08:16 +1000 Received: (qmail 25881 invoked by uid 107); 2 Aug 2011 08:08:15 +1000 Date: 2 Aug 2011 08:08:15 +1000 Date: Tue, 2 Aug 2011 08:08:15 +1000 From: Callum Gibson To: freebsd-current@freebsd.org Message-ID: <20110801220815.GA24623@omma.gibson.athome> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: panic: ffs_valloc: dup alloc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2011 00:14:32 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I have an i386 -current from late Jul 18 which is running in VirtualBox (on 8.X amd64 host). After a VM reset I seem to have hit a SUJ-related issue. On boot the system produced a "panic: ffs_valloc: dup alloc". Stack trace below (sorry had to do this as a screenshot - I don't know if you can dump text any other way): --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline; filename=p1 I took a snapshot with it sitting in DDB but I'm not sure what other information would be helpful to the FS-meisters. I can even make the whole snapshot available if someone wants it if you let me know which bits and pieces are required from the .VirtualBox directory. I booted into single user to fsck / and asked to use the journal and it found no issues. Them ee-fscking without using the journal found an unref file and some other errors. After that the system could boot normally. C -- Callum Gibson @ home http://members.optusnet.com.au/callumgibson/ --EeQfGwPcQSOJBaQU--