From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:56:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3843016A4CE for ; Mon, 6 Dec 2004 18:56:35 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED59D43D6B for ; Mon, 6 Dec 2004 18:56:34 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id D89E772DD4; Mon, 6 Dec 2004 10:56:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id D6E2F72DCB; Mon, 6 Dec 2004 10:56:34 -0800 (PST) Date: Mon, 6 Dec 2004 10:56:34 -0800 (PST) From: Doug White To: Henry Whincup In-Reply-To: <006501c4da28$5692e130$0a64a8c0@techiebod.com> Message-ID: <20041206105139.E19661@carver.gumbysoft.com> References: <006501c4da28$5692e130$0a64a8c0@techiebod.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: ffs_clusteralloc: allocated out of group on 5TB fs (5.3-Stable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 06 Dec 2004 18:56:35 -0000 On Sat, 4 Dec 2004, Henry Whincup wrote: > On a machine with a 5TB array I created a single partition via gpt and a > filesystem using the defaults from newfs. > > All seemed well until I tried to fill the partition with data. With "only" > 870GB or so used utilities started reporting the disk as full. Shortly (a > few hours) after the machine panic'd. Ooh, fun. I wish I had a 5TB array to play with :) > During this time I had been trying to copy file via nfs and rsync onto the > array. After several crashes I tried a simple "dd if=/dev/zero of=./file" > and after writing ~33GB the machine rebooted (the panic details below are > from this reboot) > > Details follow: [..] > Backtrace: > #0 0xc060ce82 in doadump () > #1 0xc060d47b in boot () > #2 0xc060d7a1 in panic () > #3 0xc073445e in ffs_clusteralloc () > #4 0xc0733680 in ffs_hashalloc () > #5 0xc07329ea in ffs_reallocblks_ufs2 () > #6 0xc073205a in ffs_reallocblks () > #7 0xc0657e7c in cluster_write () > #8 0xc074c350 in ffs_write () > #9 0xc066bf10 in vn_write () > #10 0xc062d624 in dofilewrite () > #11 0xc062d4d1 in write () > #12 0xc07bb07f in syscall () > #13 0xc07a8a0f in Xint0x80_syscall () > > Kernel is the default SMP kernel and sources are from 28th Nov 2004. > > I assume a proper debug kernel with symbols would be more helpful, but I > just wanted to know if this was a known bug - or something I have done > wrong, first. > Other than that is there anything else I can provide to help find this bug? Very large FFS filesystems have not been extensively tested. Maybe you can help :) You should be able to compile GENERIC with makeoptions "DEBUG=-g" in the config file and that will leave a kernel.debug in the compile directory that you can use. Once you get that loaded up the output of 'bt full' would be nice to have. I suspect an integer overflow in dtog(), which is a macro. 1545 if (dtog(fs, bno) != cg) 1546 panic("ffs_clusteralloc: allocated out of group"); -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org