where to ask about problems with bsdinstall in 9.0RC2?
bonomi at mail.r-bonomi.com
Sat Nov 19 15:06:54 UTC 2011
William Bulley <web at umich.edu> wrote:
> According to Fbsd8 <fbsd8 at a1poweruser.com> on Fri, 11/18/11 at 21:02:
> > I think you have under sized /usr and the uncompress ran out of space
> > during the install. Start over again, wipe the disk clean (ie: delete
> > all slices)and re-allocate your slices with larger space allocations.
IIRC, the error message was "out of inodes".
This means something was trying to put *lots* (where 'lots' is relative
number, depending on the size of the filesystem :) of little files on the
filesystem. You were _not_ out of 'free space' on the filesystem, just out
of slots for file 'metadata'. Newfs, if not told specifically how many
inodes to allocate, makes a 'guess' based on the size of the slice -- thus
increasing the size of a partition will have an automatic 'side effect' of
increasing the total number of inodes. However, by explicitly stating the
number of inodes, or the inodes per unit of storage, when running newfs,
one can get more (or fewer) inodew _without_ having to change partition
sizes. Most significantly, one can do this -- change the number of inodes,
that is -- *without* having to destroy/recreate any other partitions on
the same physical device.
SECONDLY, if this happened -during- the install, and the complaint
was about "/var" -- as distinct from something like '/a/var', or '/mnt/var'
Then the problem is *NOT* on the drives you are installing *ONTO*, but
on the media you are installing _from_. At a guess, the installer is
using /var -- probably /var/tmp -- to keep scratchpad files in, and there
are not enough inodes for the installer. could it be unpacking tarfiles
there, move/copy onto the 'target' media?
You're installing from a memory stick right? You may need to rebuild
the filesystem on the stick, _manually_ specifying a larger number of
inodes for the filesystem that /var is part of.
More information about the freebsd-questions