From owner-freebsd-fs@FreeBSD.ORG Tue Aug 1 20:54:34 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0793616A4DF for ; Tue, 1 Aug 2006 20:54:34 +0000 (UTC) (envelope-from adamsch1@yahoo.com) Received: from web31812.mail.mud.yahoo.com (web31812.mail.mud.yahoo.com [68.142.207.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 5DF3443D70 for ; Tue, 1 Aug 2006 20:54:33 +0000 (GMT) (envelope-from adamsch1@yahoo.com) Received: (qmail 54068 invoked by uid 60001); 1 Aug 2006 20:54:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=AY4J3RLomtfVxDe9a3UkQTZ76NDKlssj0yj+1qUmKToNnmXmELsTaMyZ7+YMiVA+AoaRjMMuPaVCkV9XgDcg/kRGWejOSzbmh8nra+82AX6wP+hvkWw1HwjmhLbIzGrW8CFLtaIQKywxeoIWHX0AR5p7qimeUmp15oKCDKWsBxc= ; Message-ID: <20060801205432.54066.qmail@web31812.mail.mud.yahoo.com> Received: from [207.126.230.225] by web31812.mail.mud.yahoo.com via HTTP; Tue, 01 Aug 2006 13:54:32 PDT Date: Tue, 1 Aug 2006 13:54:32 -0700 (PDT) From: Shane Adams To: freebsd-fs@FreeBSD.ORG In-Reply-To: <200607280927.k6S9RG2B072245@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: Advice for hacking on ufs/ffs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Shane Adams List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2006 20:54:34 -0000 I think I found a bug in the ffs code, specifically in ffs_uninit and the uma_zcreates in ffs_vfsops.c You need to explicitly call zdestroy on uma_inode1, uma_ufs1 and uma_ufs2 in ffs_uninit otherwise if UFS/FFS (as a kernel module) is unloaded, you get a panic if you call sysctl -a after the kldunload. Now I'm new to freebsd, and on my system UFS/FFS is statically compiled, but I was screwing around and discovered this. Not sure how to report this or the patch (that fixed the problem on my system). Shane