From owner-freebsd-bugs@FreeBSD.ORG Wed Mar 9 21:10:06 2005 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B51816A4CE for ; Wed, 9 Mar 2005 21:10:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0E4F43D48 for ; Wed, 9 Mar 2005 21:10:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j29LA5H2092608 for ; Wed, 9 Mar 2005 21:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j29LA5HL092607; Wed, 9 Mar 2005 21:10:05 GMT (envelope-from gnats) Date: Wed, 9 Mar 2005 21:10:05 GMT Message-Id: <200503092110.j29LA5HL092607@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: dpk Subject: Re: kern/41723: [2TB] on 1TB fs, copying files to filesystem causes "integer divide fault" and panic. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dpk List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 21:10:06 -0000 The following reply was made to PR kern/41723; it has been noted by GNATS. From: dpk To: freebsd-gnats-submit@freebsd.org, kreature@c2i.net Cc: Subject: Re: kern/41723: [2TB] on 1TB fs, copying files to filesystem causes "integer divide fault" and panic. Date: Wed, 9 Mar 2005 13:08:51 -0800 (PST) In answer to the above question: This bug still affects the latest version of FreeBSD, 5.3-RELEASE. Unfortunately I cannot obtain a core dump due to a separate bug involving a miscalculation of the dumpdev size. However, the backtrace is pretty similar -- the bug is still in ffs_dirpref: maxcontigdirs = min((avgbfree * fs->fs_bsize) / dirsize, 255); The above are still 32-bit ints, so I expect that it is probably still where the bug comes up.