From owner-freebsd-stable Sun Dec 10 14:15:16 2000 From owner-freebsd-stable@FreeBSD.ORG Sun Dec 10 14:15:14 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4B8E737B400 for ; Sun, 10 Dec 2000 14:15:14 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBAMFAa06957; Sun, 10 Dec 2000 14:15:10 -0800 (PST) Date: Sun, 10 Dec 2000 14:15:10 -0800 From: Alfred Perlstein To: Tom Cc: Ken Escape Meta Alt Control Shift Kanno , stable@FreeBSD.ORG Subject: Re: MFS sizes Message-ID: <20001210141509.O16205@fw.wintelcom.net> References: <20001210122732.K16205@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from tom@uniserve.com on Sun, Dec 10, 2000 at 01:18:45PM -0800 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Tom [001210 13:18] wrote: > On Sun, 10 Dec 2000, Alfred Perlstein wrote: > > > * Ken " Escape Meta Alt Control Shift Kanno [001210 12:21] wrote: > > > I am not able to create MFS ramdisks larger than about 500MB. This seems to be > > > because I nor mkfs are able to malloc more than 520185 k of RAM. I've tried 768 > > > and 1024MB of RAM in my machine as well as swap sized of 256 and 1024MB. > > > > > > is there a reason for this limit or a workaround? > > > > You need to increase MAXDSIZ in your kernel as the MFS is allocated inside > > a process's address space. > > BTW, You can just use ulimit or login.conf settings instead. The days > of recompiling the kernel for every change are nearly over. That's incorrect. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message