Sparse image
This article needs additional citations for verification. (March 2011) |
Filename extension |
.sparseimage |
---|---|
Internet media type | application/octet-stream |
Uniform Type Identifier (UTI) | com.apple.disk-image-sparse |
UTI conformation | com.apple.disk-image |
Developed by | Apple Inc. |
Type of format | disk image |
Container for | file system objects |
A sparse image is a type of disk image file that can be created under Mac OS X using Disk Utility. Encrypted sparse image files are used to secure a user's home directory by the FileVault feature in Mac OS X Snow Leopard and earlier.
Unlike a full image file (.dmg), which takes up as much actual space as the real disk it represents (regardless of the amount of unused space), a sparse image file (.sparseimage) takes up only as much actual disk space as the data contained within.
This can be advantageous when backing up data. For example, assume a user would like to make a backup of a hard disk volume named "INFO" that is 5GB in size, yet only contains 2.5GB of actual data. While a single layer DVD-R (with around 4.7GB capacity) would be too small to store a full-sized "INFO.dmg" image file, an "INFO.sparseimage" image file will fit. This is because the unused 2.5GB from the original volume is not actually allocated within the sparse image file. The "INFO.sparseimage" file will occupy only 2.5GB.
Note that if the 2.5GB "INFO.sparseimage" backup on the DVD is subsequently opened and mounted as a "clone" of the source volume, the Finder will report the clone as having the original 5GB capacity, with 2.5GB available, but the virtual disk will be "read-only", because the source image file resides on read-only media. However, the first-generation 2.5GB "INFO.sparseimage" on a hard drive, when mounted, may have files added to it until the originally designated 5GB capacity is reached. The ".sparseimage" file will expand in size to accommodate the additional data. Deleting files from the mounted virtual volume will not result in a reduction in the size of the corresponding ".sparseimage" file, but the size of the image can be reduced when the volume is not mounted.
Two limitations are therefore worth noting regarding the use of this image file format:
- A customized ".sparseimage" image file can be assigned a larger total capacity than the physical volume (or HD partition) on which it originally resides. While the virtual volume will seem to make that capacity available, attempting to exceed the physical capacity of the underlying volume will result in a disk error: "ran out of space". The ".sparseimage" file must first be moved to a larger physical disk or partition.
- As noted above, while mounted ".sparseimage" image files automatically expand to their preassigned limit when data is added, they cannot be arbitrarily resized without the use of Disk Utility, hdiutil, or other such software.
When the sparseimage file is not mounted, the .sparseimage file may be resized using Disk Utility’s Resize Image function. Sparseimages may also be resized from the Terminal. The following example resizes a .sparseimage so that it can expand to a maximum size of 50 gigabytes:
hdiutil resize -size 50g MyFile.sparseimage
Similarly, a .sparseimage file that has expanded in size but then had files deleted, can be "compacted" to a smaller size with the following command:
hdiutil compact MyFile.sparseimage
Additional information about the hdiutil
command may be seen by typing the following in the Terminal:
man hdiutil
If it doesn't match, it means you have a disk image with a partition map.
- Unmount / eject disk
- Select the disk image (the .sparsebundle / .sparseimage) in Disk Utility
- Select the Partition tab
- Drag the corner to enlarge partiton to the desired size
- Apply
Sparse bundle disk images
Mac OS X v10.5 (Leopard) introduced the concept of the sparse bundle.[1] Instead of a monolithic file, a sparse bundle is a bundle (directory) containing a number of files called bands, each in the order of 8 MB in size. This means even though to the end user the sparse bundle appears as a single file, it is composed of smaller files. As of Mac OS X 10.8, the bands are 8.4 MB each. When the content of the image changes, one or more band files is changed, created, or deleted. This allows backup software (such as Time Machine) to operate more efficiently. You may use a tool such as rsync to keep your disk image(s) consistent across various systems.[2]
References
- ^ ScottW (November 5th, 2007). "Live FileVault and Sparse Bundle Backups in Leopard". http://macosx.com. Retrieved January 21, 2013.
{{cite web}}
: Check date values in:|date=
(help); External link in
(help)|work=
- ^ "Backing up Sparse Bundle Images Over SSH". LBackup. Retrieved January 21, 2013.