Disk volume

Also known as: volume

On this page 7

A disk volume, often simply called a volume, is a single addressable storage area formatted with one file system that an operating system can mount and present to users as a drive letter, a mount point or an icon. In desktop operating systems, the volume is the unit that users actually see and use, while the partitions, physical disks and containers underneath remain mostly hidden.

A volume is a logical construct, not a physical one. It often matches one partition on one disk, but it can also span several disks, live inside a container shared with other volumes, or exist as an image file. Understanding that distinction explains why tools such as Disk Management, Disk Utility or LVM show storage in layers, and why resizing, encrypting and backing up behave differently at each layer.

How a disk volume relates to disks and partitions

A disk volume sits above the partition layer and below the file system’s directory tree. The physical disk is divided by a partition table such as GPT or MBR into partitions; a volume manager or the operating system then exposes one or more of those areas as volumes; finally, formatting writes a file system such as NTFS, APFS, ext4 or exFAT onto each volume.

The table below separates the layers that are frequently confused, because the words partition, volume and drive are used loosely in everyday speech.

LayerWhat it isTypical example
Physical diskThe hardware device with fixed capacityA 1 TB NVMe SSD
PartitionA contiguous range of sectors defined in the partition tableA 500 GB GPT partition
VolumeA logical storage area ready to hold one file systemThe Windows C: volume
File systemThe structure that organizes files and metadataNTFS, APFS or ext4
Mount pointThe place where users reach the volumeA drive letter or /home
Storage layers from hardware to files

Each volume carries a volume identifier, such as a volume GUID on Windows or a UUID on macOS and Linux. Systems use that identifier instead of a disk position, so a volume keeps its identity even when cables, ports or boot order change.

Types of disk volumes

Operating systems support several volume layouts, which differ in how many disks they use and whether they add redundancy. The choice affects capacity, speed and the consequences of a single drive failure.

Volume typeDisks usedRedundancyKey trade-off
Simple volumeOne partition on one diskNoneEasiest to manage, single point of failure
Spanned volumeSpace joined from several disksNoneLarge capacity, but one failed disk loses data
Striped volumeData split across two or more disksNoneHigher throughput, higher failure risk
Mirrored volumeIdentical copies on two disksFull copySurvives one disk failure, halves usable space
Container volumeShares free space inside one containerDepends on containerFlexible sizing, shared space can run out
Common volume layouts and their trade-offs

Apple’s APFS containers illustrate the last type: several volumes, such as System, Data and Preboot, share one pool of free space and grow on demand. Linux Logical Volume Manager (LVM) and Windows Storage Spaces provide similar pooling, allowing a volume to be enlarged without moving neighboring partitions.

The disk volume overlaps with several neighboring concepts, and mixing them up leads to wrong commands, such as formatting a whole disk when only one volume needed repair. The comparison below clarifies the boundaries.

ConceptScopeRelationship to a volume
Disk partitionA sector range on one diskOften holds exactly one simple volume
Disk imageA file containing a whole volume or diskCan be mounted as a volume
Disk formattingAn operation, not a structureCreates a file system on a volume
Disk quotaA per-user usage limitApplies inside a volume
Recovery partitionA special-purpose areaUsually a hidden volume without a drive letter
Volume versus neighboring concepts

A practical rule follows from this table: partitions describe where data sits, while volumes describe what the operating system mounts. Encryption, quotas, shadow copies and snapshots are usually configured per volume, not per disk.

Creating and managing volumes

Volume management covers creating, formatting, resizing, mounting and checking volumes. Windows offers Disk Management and the diskpart command, macOS provides Disk Utility and the diskutil command, and Linux uses tools such as lsblk, LVM commands and mkfs.

  • Choose the file system for the use case: NTFS or APFS for system volumes, exFAT for removable volumes shared between platforms.
  • Pick a suitable allocation unit size, because large clusters waste space with many small files.
  • Assign a meaningful volume label, which helps users identify the correct target before destructive actions.
  • Check the volume regularly with chkdsk, First Aid or fsck after unexpected power loss.

Resizing deserves particular care. Shrinking a volume works only when unmovable files, such as page files or metadata, do not occupy the end of the volume, and extending a simple volume usually requires unallocated space directly after it.

Limitations and common mistakes with volumes

The most damaging mistakes involve selecting the wrong volume for a destructive operation. Drive letters change between sessions and machines, so formatting by letter alone is risky, while checking the label, size and identifier first prevents most accidents.

SymptomLikely causeFix
Volume shows as RAWDamaged or unrecognized file systemRecover data first, then reformat
Extend option is unavailableNo adjacent unallocated spaceUse a container, LVM or move partitions
Volume not visible on another OSUnsupported file systemUse exFAT for cross-platform media
Free space disappears quicklySnapshots or shared container spaceReview snapshots and container usage
Typical volume problems and fixes

Another misconception is that multiple volumes on one disk provide backup. If the physical disk fails, every volume on it fails together, so real protection requires copies on separate physical media.

The short version

A disk volume is one usable storage space that your computer shows as a drive, such as C: on Windows or Macintosh HD on a Mac. The physical disk is like a warehouse. Volumes are the separate rooms built inside it.

Each room has its own filing system and its own name. You can have several rooms on one disk, or one large room spread over several disks. However, if the warehouse burns down, every room inside is lost together.

Where it makes a difference

A video editor works on a desktop computer with a 2 TB SSD and two 4 TB hard drives. The SSD holds the system volume, while the two hard drives were originally combined into one 8 TB striped volume for fast access to raw footage.

When one hard drive developed bad sectors, the striped volume became unreadable and three days of footage were lost, because striping offers no redundancy. The editor rebuilt the drives as a 4 TB mirrored volume for active projects and added a separate external volume for nightly backups, formatted with exFAT so that a colleague’s computer could read it.

Usable capacity halved, but a later drive failure caused no data loss and no downtime: the mirror continued working while the failed disk was replaced and resynchronized overnight.