Chapter 28 Disk Management (Overview)

This overview chapter provides conceptual information about Solaris disk slices and introduces the format utility.

This is a list of the overview information in this chapter.

• "Disk Terminology"

• "About Disk Slices"

• "SPARC: Disk Slices"

• "IA: Disk Slices"

• "Determining Which Slices to Use"

• "The format Utility"

• "Guidelines for Using the format Utility"

• "Formatting a Disk"

• "About Disk Labels"

• "Partition Table"

For instructions on how to add a disk drive to your system, see Chapter 30, SPARC: Adding a Disk (Tasks) or Chapter 31, IA: Adding a Disk (Tasks).

What's New in Disk Management?

This section describes features introduced in the Solaris 8 release.

IA: Support for Large Disks

This Solaris release fully uses disks larger than 8 Gbytes because of improved BIOS interfaces. Previously, the following limitations impacted IA based systems running the Solaris Intel Platform Edition:

• On IDE disks, only the first 8 Gbytes could be used by the system.

• On either SCSI or IDE disks, only the first 8 Gbytes could only be used for the root (/) slice.

Both of these restrictions have been removed on systems with improved BIOSes.

See Solaris 8 (Intel Platform Edition) Installation Guide for more information.

Where to Find Disk Management Tasks

Use these references to find step-by-step instructions for managing disks.

• Chapter 30, SPARC: Adding a Disk (Tasks)

• Chapter 31, IA: Adding a Disk (Tasks)

Introduction

Managing disks in the Solaris environment usually involves setting up the system and running the Solaris installation program to create the appropriate disk slices and install the operating system. Occasionally, you might need to use the format utility to add a new disk drive or replace a defective one.

Disk Terminology

Before you can effectively use the information in this section, you should be familiar with basic disk architecture. In particular, you should be familiar with the following terms:

• Track

• Cylinder

• Sector

• Disk controller

• Disk label

• Device drivers

If you are unfamiliar with these terms, refer to the glossary (for a brief definition) or product information from the disk's manufacturer.

About Disk Slices

Files stored on a disk are contained in file systems. Each file system on a disk is assigned to a slice--a group of cylinders set aside for use by that file system. Each disk slice appears to the operating system (and to the system administrator) as though it were a separate disk drive.

See Chapter 34, Managing File Systems (Overview) for information about file systems.

Slices are sometimes referred to as partitions. This book uses slice but certain interfaces, such as the format utility, refer to slices as partitions.

When setting up slices, remember these rules:

• Each disk slice holds only one file system.

• No file system can span multiple slices.

Slices are set up slightly differently on SPARC and IA platforms. The table below summarizes the differences:

SPARC: Disk Slices

On SPARC based systems, Solaris defines eight disk slices and assigns to each a conventional use. These slices are numbered 0 through 7. The table below summarizes the contents of the eight Solaris slices on a SPARC based system.

IA: Disk Slices

On IA based systems, disks are divided into fdisk partitions. An fdisk partition is a section of the disk reserved for a particular operating environment, such as Solaris.

Solaris places ten slices, numbered 0-9, on a Solaris fdisk partition as shown in the following table.

Using Raw Data Slices

The SunOS operating system stores the disk label in block 0, cylinder 0 of each disk. This means that using third-party database applications that create raw data slices must not start at block 0, cylinder 0, or the disk label will be overwritten and the data on the disk will be inaccessible.

Do not use the following areas of the disk for raw data slices, which are sometimes created by third-party database applications:

1. Block 0, cylinder 0, where the disk label is stored.

2. Avoid cylinder 0 entirely for improved performance.

3. Slice 2, which represents the entire disk.

Slice Arrangements on Multiple Disks

Although a single disk that is large enough can hold all slices and their corresponding file systems, two or more disks are often used to hold a system's slices and file systems.

A slice cannot be split between two or more disks. However, multiple swap slices on separate disks are allowed.

For instance, a single disk might hold the root (/) file system, a swap area, and the /usr file system, while a separate disk is provided for the /export/home file system and other file systems containing user data.

In a multiple disk arrangement, the disk containing the operating system software and swap space (that is, the disk holding the root (/) or /usr file systems or the slice for swap space) is called the system disk. Disks other than the system disk are called secondary disks or non-system disks.

Locating a system's file systems on multiple disks allows you to modify file systems and slices on the secondary disks without having to shut down the system or reload operating system software.

Having more than one disk also increases input-output (I/O) volume. By distributing disk load across multiple disks, you can avoid I/O bottlenecks.

Determining Which Slices to Use

When you set up a disk's file systems, you choose not only the size of each slice, but also which slices to use. Your decisions about these matters depend on the configuration of the system to which the disk is attached and the software you want to install on the disk.

The system configurations are:

• Servers

• Standalone systems

Each system configuration requires the use of different slices. The table below lists these requirements.

See "Overview of System Types" for more information about system configurations.

The Solaris installation program provides slice size recommendations based on the software you select for installation.

The format Utility

Read the following information if you want to see a conceptual view of the format utility and it uses before proceeding to the "how-to" or reference sections.

Definition

The format utility is a system administration tool used to prepare hard disk drives for use on your Solaris system. The format utility cannot be used on diskette drives, CD-ROM drives, or tape drives.

Features and Benefits

The table below shows the features and associated benefits that the format utility provides.

All of the options of the format utility are fully described in Chapter 32, The format Utility (Reference).

When to Use the format Utility

Disk drives are partitioned and labeled by the Solaris installation program as part of installing the Solaris release. You might need to use the format utility when:

• Displaying slice information

• Dividing a disk into slices

• Adding a disk drive to an existing system

• Formatting a disk drive

• Repairing a disk drive

The main reason a system administrator uses the format utility is to divide a disk into disk slices. These steps are covered in Chapter 30, SPARC: Adding a Disk (Tasks) and Chapter 31, IA: Adding a Disk (Tasks).

See the section below for guidelines on using the format utility.

Guidelines for Using the format Utility

Formatting a Disk

In most cases, disks are formatted by the manufacturer or reseller and do not need to be reformatted when you install the drive. To determine whether or not a disk is formatted, use the format utility. See "How to Determine if a Disk is Formatted" for more information.

If you determine that a disk is not formatted, use the format utility to format the disk.

Formatting a disk accomplishes two steps:

• Preparing disk media for use

• Compiling a list of disk defects based on a surface analysis

Formatting is a destructive process--it overwrites data on the disk. For this reason, disks are usually formatted only by the manufacturer or reseller. If you think disk defects are causing recurring problems, you can use the format utility to do a surface analysis, but be careful to use only the commands that do not destroy data. See "How to Format a Disk" for details.

A small percentage of total disk space available for data is used to store defect and formatting information. This percentage varies according to disk geometry, and decreases as the disk ages and develops more defects.

Formatting might take anywhere from a few minutes to several hours, depending on the type and size of the disk.

About Disk Labels

A special area of every disk is set aside for storing information about the disk's controller, geometry, and slices. That information is called the disk's label. Another term used to described the disk label is the VTOC (Volume Table of Contents). To label a disk means to write slice information onto the disk. You usually label a disk after changing its slices.

If you fail to label a disk after creating slices, the slices will be unavailable because the operating system has no way of "knowing" about the slices.

Partition Table

An important part of the disk label is the partition table which identifies a disk's slices, the slice boundaries (in cylinders), and total size of the slices. A disk's partition table can be displayed using the format utility. The table below describes partition table terminology.

Partition flags and tags are assigned by convention and require no maintenance.

See "How to Display Disk Slice Information" or "How to Examine a Disk Label" for more information on displaying the partition table.

Examples--Partition Tables

The following partition table example is displayed from a 1.05-Gbyte disk using the format utility:

Total disk cylinders available: 2036 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0       root    wm       0 -  300      148.15MB    (301/0/0)   303408
  1       swap    wu     301 -  524      110.25MB    (224/0/0)   225792
  2     backup    wm       0 - 2035     1002.09MB    (2036/0/0) 2052288
  3 unassigned    wm       0               0         (0/0/0)          0
  4 unassigned    wm       0               0         (0/0/0)          0
  5 unassigned    wm       0               0         (0/0/0)          0
  6        usr    wm     525 - 2035      743.70MB    (1511/0/0) 1523088
  7 unassigned    wm       0               0         (0/0/0)          0

The partition table contains the following information:

The following example displays a disk label using the prtvtoc command.

# prtvtoc /dev/rdsk/c0t1d0s0
* /dev/rdsk/c0t1d0s0 partition map
*
* Dimensions:
*     512 bytes/sector
*      72 sectors/track
*      14 tracks/cylinder
*    1008 sectors/cylinder
*    2038 cylinders
*    2036 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00          0    303408    303407   /
       1      3    01     303408    225792    529199
       2      5    00          0   2052288   2052287
       6      4    00     529200   1523088   2052287   /usr

The disk label includes the following information:

Dimensions - This section describes the physical dimensions of the disk drive.

Flags - This section describes the flags listed in the partition table section. See Table 28-7 for a description of partition flags.

Partition (or Slice) Table - This section contains the following information:

Dividing a Disk Into Slices

The format utility is most often used by system administrators to divide a disk into slices. The steps are:

• Determining which slices are needed

• Determining the size of each slice

• Using the format utility to divide the disk into slices

• Labeling the disk with new slice information

• Creating the file system for each slice

The easiest way to divide a disk into slices is to use the modify command from the partition menu. The modify command allows you to create slices by specifying the size of each slice in megabytes without having to keep track of starting cylinder boundaries. It also keeps tracks of any disk space remainder in the "free hog" slice.

Using the Free Hog Slice

When you use the format utility to change the size of one or more disk slices, you designate a temporary slice that will expand and shrink to accommodate the resizing operations.

This temporary slice donates, or "frees," space when you expand a slice, and receives, or "hogs," the discarded space when you shrink a slice. For this reason, the donor slice is sometimes called the free hog.

The donor slice exists only during installation or when you run the format utility. There is no permanent donor slice during day-to-day, normal operations.

See "SPARC: How to Create Disk Slices and Label a Disk" or "IA: How to Create Disk Slices and Label a Disk" for information on using the free hog slice.