On larger platforms, functional issues such as backup strategies and required filesystem sizes can dictate disk layout. For example, suppose a file server is to be constructed serving 100 GB of executable data files to end users via NFS. Such a system will need enough resources to compartmentalize various parts of the directory tree into separate filesystems and might look like this:
100 MB. Keep kernels under the 1024-cylinder limit.
1 GB, depending on RAM.
500 MB (minimum).
4 GB. All of the executables in /usr are shared to workstations via read-only NFS.
2 GB. Since log files are in their own partition, they won’t threaten system stability if the filesystem is full.
500 MB. Since temporary files are in their own partition, they won’t threaten system stability if the filesystem is full.
90 GB. This big partition takes up the vast bulk of available space, offered to users for their home directories and data.
On production servers, much of the system is often placed on redundant media, such as mirrored disks. Large filesystems, such as /home, may be stored on some form of disk array using a hardware controller.