From owner-freebsd-questions@FreeBSD.ORG Thu Jun 9 06:10:49 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1874416A41C for ; Thu, 9 Jun 2005 06:10:49 +0000 (GMT) (envelope-from Frantisek.Rysanek@post.cz) Received: from mail.fccps.cz (mail.fccps.cz [195.146.112.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BB0A43D1D for ; Thu, 9 Jun 2005 06:10:48 +0000 (GMT) (envelope-from Frantisek.Rysanek@post.cz) Received: from localhost (localhost [127.0.0.1]) by mail.fccps.cz (Postfix) with ESMTP id E330677C85; Thu, 9 Jun 2005 08:10:46 +0200 (CEST) Received: from mail.fccps.cz ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10798-04; Thu, 9 Jun 2005 08:10:45 +0200 (CEST) Received: from frr (frr.in.fccps.cz [192.168.2.14]) by mail.fccps.cz (Postfix) with ESMTP id C3D2877C7C; Thu, 9 Jun 2005 08:10:42 +0200 (CEST) From: "Frantisek Rysanek" To: freebsd-questions@freebsd.org Date: Thu, 09 Jun 2005 08:16:19 +0200 MIME-Version: 1.0 Message-ID: <42A7FAD3.5051.98EB5B15@localhost> Priority: normal In-reply-to: <42A70833.806@dial.pipex.com> References: <42A717EB.8095.9574FF2F@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at fccps.cz Cc: xfb52@dial.pipex.com Subject: Summary: 12TB GEOM stripe, newfs, then fsck: cannot alloc 768053748 bytes for blockmap X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 06:10:49 -0000 Thanks a lot to Mr. Zbyslaw. Being too lazy myself to fiddle with the soft limit via the shell or bootloader, I did the following in the kernel build config file: options MAXDSIZ=(1024UL*1024*1024) options DFLDSIZ=(1024UL*1024*1024) This way, fsck works just fine. To address other people's suggestions: I haven't tried to force the fsck under the old limit. A local friend has suggested to increase the block size to newfs, or something along those lines - essentially to decrease the FS overhead and the size of the "blockmap". I haven't tried that but I guess it sounds reasonable - may make sense on machines where you just can't get enough RAM or are not willing to grant it all to a single process. Thanks to everyone who replied :-) Frank Rysanek On 8 Jun 2005 at 16:01, Alex Zbyslaw wrote: > >cannot alloc 768053748 bytes for blockmap > > > Do you have MAXDSIZ set in your kernel? And what about any limits? > > e.g. I have options MAXDSIZ=(1024UL*1024*1024) > and "limit memoryuse unlimited"