From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 9 20:20:07 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8BE616A400 for ; Mon, 9 Apr 2007 20:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id A8FF613C4BC for ; Mon, 9 Apr 2007 20:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l39KK7Q8079135 for ; Mon, 9 Apr 2007 20:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l39KK7SC079134; Mon, 9 Apr 2007 20:20:07 GMT (envelope-from gnats) Date: Mon, 9 Apr 2007 20:20:07 GMT Message-Id: <200704092020.l39KK7SC079134@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jan Srzednicki Cc: Subject: Re: bin/111146: fsck fails on 6Tfilesystem X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jan Srzednicki List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2007 20:20:07 -0000 The following reply was made to PR bin/111146; it has been noted by GNATS. From: Jan Srzednicki To: Dan D Niles Cc: bug-followup@FreeBSD.org Subject: Re: bin/111146: fsck fails on 6Tfilesystem Date: Mon, 9 Apr 2007 22:13:36 +0200 On Mon, Apr 09, 2007 at 03:09:28PM -0500, Dan D Niles wrote: > On Mon, 2007-04-09 at 21:48 +0200, Jan Srzednicki wrote: > > Check with dumpfs how many inodes are there in your filesystem. > > dumpfs seg-faulted and dumped core. It spit out this info before core > dumping: That's kinda strange, dumpfs never did that to me. It appears to me that this filesystem has got quite severely corrupted. Did you try newfs on it? And another thing: try tuning up the -i, -f and -b parameters to newfs. I assume that on such a big filesystem average filesize will be much bigger than the "UNIX default" (10k), so you can safely set these to their maximums (and allocate inodes more scarcely). -- Jan Srzednicki :: http://wrzask.pl/ "Remember, remember, the fifth of November" -- V for Vendetta