Technical article 100095

"Out of inodes" error when creating boot/root floppy with mkarcboot command.

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

When using the mkarcboot command to create a boot/root floppy set, the system responds with error messages similar to the following:

NOTICE: HTFS: Out of inodes on EAFS dev marry (76/1)

-or-

/etc/conf/bin/idmknod: Cannot make character special /mnt/dev/vsdsp/vsdsp61: No space left on device (error 28)

The floppy creation process then fails.
NOTICE:  This is NOT the same problem that occurs when creating a
boot/root floppy disk set with the standard mkdev(ADM) fd command.
See TA104822, "'Out of inodes' error when creating boot/root
floppies on OpenServer 5." for a solution to this problem when
creating regular boot/root floppy sets.

Solution

The best solution is to eliminate unnecessary device nodes that will
be created on the diskette.  Many devices are not required in an
emergency boot environment, but each requires an inode.

To eliminate unwanted device nodes follow these steps:

1. Log in as root.
2. Change to the directory /usr/lib/arcboot

3. Back up the .mkfuncs script with the following command:

cp .mkfuncs .mkfuncs.orig

4. Open the file in a text editor and find the following lines:

NOTREQ="aud byte cbd cdt da dup ecc_ eisarom err log marry pa\ prf ptm ptspwr uapm rtc sleeper"

These are the devices from node.d that will be excluded from the root diskette.

5.  Change the word ptspwr to two words: pts pwr.  If it is
already two words, leave it as is.
6.  Add the following words:

merge mpm spm svdsp svkbd vdsp vkbd vmouse spt mpt

The line should now look like this:

NOTREQ="aud byte cbd cdt da dup ecc_ eisarom err log marry pa\
       prf ptm pts pwr uapm rtc sleeper merge mpm spm svdsp\
       svkbd vdsp vkbd vmouse spt mpt"
7.  Save the file ".mkfuncs" and run mkarcboot.  You should almost
certainly be able to create the floppy now.
8.  If you are still running out of inodes, run the following
command:
wc -l /etc/conf/node.d/* | sort -nr | more
This will list all the devices in the link kit along with the
number of nodes that will be created for each.  If you see any
you can do without in an emergency boot situation, add that
device name to the NOTREQ list.  An example would be if you
have a multi-port board or a terminal server configured.

9. ALWAYS test any boot/root floppy set to be sure you have all the functionality you will need in an emergency recovery situation.

Another solution is to increase the number of inodes that will be
created on the floppies.  Each extra inode will use 128 bytes on
the root filesystem and may require a second root disk to ensure
that all of the necessary utilities will be copied to the root
diskette(s).  Therefore the mkarcboot process may require a total
of three 1.44 meg floppy diskettes (1 for the boot diskette and
2 for the root diskettes).

Follow the steps below to modify the mkarcboot process to allow for the creation of the additional inodes:

1. Log in as root.
2. Change to the directory /usr/lib/arcboot

3. Back up the .mkfuncs script with the following command:

cp .mkfuncs .mkfuncs.orig
4. Open the file in a text editor and search for the text string
1000.  There will be two lines that need modification; they
look like this before modification:
/etc/mkfs -y -f EAFS /dev/marry/tmp/ramdisk 5120:1000 >/dev/null 2>&1
else
/etc/mkfs -y -f EAFS /dev/marry/tmp/ramdisk 5220:1000 >/dev/null 2>&1
The value of 1000 is the default number of inodes that will be
created on the floppy diskettes.  Change the value from 1000 to 1500
so that the lines look like this:
/etc/mkfs -y -f EAFS /dev/marry/tmp/ramdisk 5120:1500 >/dev/null 2>&1
else
/etc/mkfs -y -f EAFS /dev/marry/tmp/ramdisk 5220:1500 >/dev/null 2>&1
5.  Save the file ".mkfuncs" and run mkarcboot.  You should almost
certainly be able to create the floppy now.

6. ALWAYS test any boot/root floppy set to be sure you have all the functionality you will need in an emergency recovery situation.

From the Xinuos technical article database, record 100095. Reproduced with permission. The original is at www.sco.com/ta/100095, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.