From nobody@FreeBSD.org  Fri Aug 16 07:52:59 2002
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4D90737B400
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Aug 2002 07:52:59 -0700 (PDT)
Received: from www.freebsd.org (www.FreeBSD.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C88AB43E6E
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Aug 2002 07:52:58 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.4/8.12.4) with ESMTP id g7GEqvOT031796
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Aug 2002 07:52:57 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.4/8.12.4/Submit) id g7GEqvvZ031795;
	Fri, 16 Aug 2002 07:52:57 -0700 (PDT)
Message-Id: <200208161452.g7GEqvvZ031795@www.freebsd.org>
Date: Fri, 16 Aug 2002 07:52:57 -0700 (PDT)
From: walter harms <wharms@bfs.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: setup uses a to small disk
X-Send-Pr-Version: www-1.0

>Number:         41711
>Category:       misc
>Synopsis:       setup uses a to small disk
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    ceri
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 16 08:00:06 PDT 2002
>Closed-Date:    Sun Jun 08 11:03:40 PDT 2003
>Last-Modified:  Sun Jun 08 11:03:40 PDT 2003
>Originator:     walter harms
>Release:        4.6 release for alpha
>Organization:
bfs
>Environment:
>Description:
I have installed bsd boot from floppy.
select A (autoconfig of hardisks),
standard install (etc..)
Then i installed via NFS from the Freebsd CD.

The config broke because i  have a 2G HD (i used only one) configured
and the configutility tried to put more on it. So while
copying it run out-of-diskspace.

I would ask for:
- please do a check for size first before installing

if the write fails you can retry or continue to next
that is useless if write failed because of diskspace. An abort
is better.

   





>How-To-Repeat:
 Install on a to small disk 
>Fix:
      
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: schweikh 
State-Changed-When: Sat Aug 17 00:02:41 PDT 2002 
State-Changed-Why:  
Please be more specific: 
- How big exactly was the slice(s)? 
- How big were the partitions chosen by syinstall's autoconfig option? 
- What partition was it running out of space on? 
- Which distributions did you select to install? 
- Have you selected to install the ports tree? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=41711 

From: Jens Schweikhardt <schweikh@schweikhardt.net>
To: Walter Harms <WHarms@bfs.de>
Cc: GNATS Bug Followup <bug-followup@FreeBSD.org>
Subject: Re: Re: misc/41711: setup uses a to small disk
Date: Sun, 18 Aug 2002 18:22:27 +0200

 Walter,
 
 On Sat, Aug 17, 2002 at 12:14:57PM +0100, Walter Harms wrote:
 # sorry i am not familar with BSD specify things this is my first encounter
 # with a bsd installation. Therefor i lack the knowlegde about the configtools
 # etc.
 # 
 # After the Std. installation failed i made a minimal installation so i got
 # a mixture that my hide some important information and does not contain
 # certain tools. (e.g i have no telnetd or sshd so i cant lock in via network
 # and need to copy anything by hand).
 # 
 # I will keep the system in these stade for a while so you can ask specific
 # thing but next WE (or better before) i plan to reinstall to get at least
 # a working system.
 # - How big exactly was the slice(s)?
 # - How big were the partitions chosen by syinstall's autoconfig option?
 # 
 # The whole disk was 2G. 
 # ca. 1.3G swap
 
 This is waaay to much swap on a 2G disk. How much RAM do you have?
 The old rule of swap=4*RAM is not valid anymore. swap=RAM is often plenty,
 you might even run without any swap at all.
 
 # Auto configured 
 # 
 # size (1k)   usage(%)  mountpoint
 # 128990        39      /
 # 218670        0       /tmp
 # 144100        102     /usr
 # 218670         0      /var
 
 I can't believe only 144M were allocated to /usr. Sysinstall is known to
 have problems when resuming a failed installation. Have you tried starting
 all over again or resuming a previous install?
 
 # - What partition was it running out of space on?
 # 
 # /usr the 102% was something confusing
 
 /usr should at least be 250M (that's what is filled on my system right
 now, with /usr/src, /usr/ports and /usr/local being different
 partitions). If you want to compile everything from scratch, go towards
 600MB.
 The >100% is due to 8% being reserved for root, so disks are full at 108%.
 
 # - Have you selected to install the ports tree?
 # i choose the Standard installation
 # later minimal.
 
 Okay, you will be asked for the ports tree after that. It's 30M in /usr/ports
 but needs a lot of files (i.e. inodes, which are a fixed number per file
 system).
 
 # suggestion:
 # Teach the installer about minimum requirement.  Then grow from there.
 # I guess the 2G would be big enought to hold the entire CD but the
 # 1.3G Swapspace brakes the calculation (ca. 780MB ram *2 ).
 
 Ah, that's were you got the number from:
 
   Swap space is a little tricker, and the rule of "2 * MEM" is simply a
   best-guess approximation and not necessarily accurate for your
   intended usage of the system. If you intend to use the system heavily
   in a server or multi-user application, you may be well advised to
   increase this size. You may also create swap space on multiple drives
   for a larger "total" swap and this is, in fact, recommended if you
   have multiple, fast drives for which such load-balancing can only help
   overall I/O performance.
 
 Well, you have an unusual system: heaps of RAM, tiny disk space.
 The sysinstall defaults and help text are good for RAM << diskspace.
 
 # perhaps you can boot here again and check if the installation
 # is working. 
 # 
 # An other problem is the whole logic of installing. when the installation
 # breaks because of lack of space the system tries to install further.
 # lack of space is a major error and should at least stop and go the main menu.
 
 I'm afraid this failure mode is too rare and hard to reproduce on purpose
 for anyone to investigate. Development of sysinstall is virtually ended
 in favor of a completely new system, so don't expect to much. It's age
 shows and it has it's quirks that probably won't get resolved before it is
 retired.
 
 # feel free to ask about more details. i will keep that (broken) state for 
 # the moment.
 
 Please reinstall from scratch with less swap (say 256M), that should
 allocate almost all your extra space to /usr.
 
 Regards,
 
 	Jens
 -- 
 Jens Schweikhardt http://www.schweikhardt.net/
 SIGSIG -- signature too long (core dumped)
State-Changed-From-To: feedback->closed 
State-Changed-By: ceri 
State-Changed-When: Sun Jun 8 11:03:38 PDT 2003 
State-Changed-Why:  
Feedback timeout (6 months or more). 
I will handle any feedback that this closure generates. 


Responsible-Changed-From-To: freebsd-bugs->ceri 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Sun Jun 8 11:03:38 PDT 2003 
Responsible-Changed-Why:  
Feedback timeout (6 months or more). 
I will handle any feedback that this closure generates. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=41711 
>Unformatted:
