Problems with Large Systems

After a system is cold-installed, you may wish to add all the file systems that existed under the previous installation, either manually or using sam. However, for a large number of file systems (for example, over a hundred), some tables in the kernel may be too small to allow correct booting. This is because the newly-installed kernel contains default values for kernel tables sizes, and does not allow for special configurations made to the previous kernel.

For example, the first boot after adding the file systems may result in error messages displayed to the console, such as:

inode:  table is full
proc:  table is full
file: table is full

The boot may fail in other ways. For example, you may have to repair the file system manually:

The kernel may need to be re-configured before booting. The following settings should allow the kernel to be booted, but may not be optimal for performance:
ninode = 2048 (default is 476) nproc = 1024 (default is 276) nfile = 2048 (default is 790)
Alternatively, you may re-configure the kernel using one of these methods:
- Select an appropriate bundle of sam-tuned parameters from sam’s kernel configuration Actions menu.
- Raise maxusers to a large value, such as 200.

Determine the correct configuration for your system.

Problems with Large Systems

Technical documentation

» Table of Contents

» Index