From owner-freebsd-hackers Sat Jul 17 18:28:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 451AC14F6B for ; Sat, 17 Jul 1999 18:28:02 -0700 (PDT) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id 57457258; Sat, 17 Jul 1999 21:28:02 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with SMTP id 459F6244; Sat, 17 Jul 1999 21:28:02 -0400 (EDT) Date: Sat, 17 Jul 1999 21:28:02 -0400 (EDT) From: David Miller To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 650 MB MFS? In-Reply-To: <199907152006.NAA12783@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Jul 1999, Matthew Dillon wrote: > : > :Are there any design limits to mfs? I want to use cdrecord to write to a > :dozen or so CD's at once, and fear making lots of coasters if I run them > :all off a single on-disk file. However, a CD only holds 650 MB, so it > :seems like I could have the image on mfs and sleep well sans coasters. > : > :Would FreeBSD handle an mfs of this size? > > Well, if you have 650MB of ram available... I suppose. > Otherwise MFS is just going to shove the data into > swap. These days 650 isn't that hard:) > > The answer is, yes you can create an MFS partition that > large. You have to make sure that you have sufficient > swap available and that your datasize resource limit is > big enough. > > So, checklist: > > * You will need 650MB of swap, possibly even more. > (unless you have 650MB+ of ram in your system) > > * from csh, 'unlimit data' then type 'limit' to > see what your maximum datasize limit is. You > may have to reconfigure your kernel to increase > it: > > options "MAXDSIZ=(1024*1024*1024)" Thanks, this is an easy one to overlook:) > * Look into using the VN device instead of MFS. > VN allows you to create a 'disk file' and then > turn it into a partition that you can then > mount and use normally. I'm not sure what good that will do me. The point of the exercise is to ensure that cdrecord never has to wait on enough seeks to create coasters. Putting it all in ram before starting should do this, but a different interface to the same data on disk doesn't. Unless I'm missing something, which is usually the case:) Thanks for the answers Matt! --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message