Logical Disk Manager
≈ 10 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
The Logical Disk Manager (LDM) is an implementation of a logical volume manager for Microsoft Windows NT, developed by Microsoft and Veritas Software. It was introduced with the Windows 2000 operating system, and is supported in Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows 8, Windows 10 and Windows 11. The MMC-based Disk Management snap-in ( ) hosts the Logical Disk Manager. On Windows 8 and Windows Server 2012, Microsoft deprecated LDM in favor of Storage Spaces. Logical Disk Manager enables disk volumes to be dynamic, in contrast to the standard basic volume format. Basic volumes and dynamic volumes differ in their ability to extend storage beyond one physical disk. Basic partitions are restricted to a fixed size on one physical disk. Dynamic volumes can be enlarged to include more free space - either from the same disk or another physical disk. (For more information on the difference, see Basic and dynamic disks and volumes, below.)
The Logical Disk Manager (LDM) is an implementation of a logical volume manager for Microsoft Windows NT, developed by Microsoft and Veritas Software. It was introduced with the Windows 2000 operating system, and is supported in Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows 8, Windows 10 and Windows 11. The MMC-based Disk Management snap-in ( ) hosts the Logical Disk Manager. On Windows 8 and Windows Server 2012, Microsoft deprecated LDM in favor of Storage Spaces. Logical Disk Manager enables disk volumes to be dynamic, in contrast to the standard basic volume format. Basic volumes and dynamic volumes differ in their ability to extend storage beyond one physical disk. Basic partitions are restricted to a fixed size on one physical disk. Dynamic volumes can be enlarged to include more free space - either from the same disk or another physical disk. (For more information on the difference, see Basic and dynamic disks and volumes, below.)
Basic and dynamic disks and volumes
Dynamic disk is a proprietary format of Microsoft developed together with Veritas. A basic volume is a volume stored on a basic disk, while a dynamic volume is a volume stored on a dynamic disk. Basic volumes and dynamic volumes differ in ability to extend storage beyond one physical disk. The basic partitions are confined to one disk and their size is fixed. Dynamic volumes allow to adjust size and to add more free space either from the same disk or another physical disk. Striped volumes (RAID 0) and spanned volumes (SPAN) are dynamic volumes using space on different physical disks. In Windows XP, spanned volume can use a maximum of 32 physical disks. The main differences between basic and dynamic disks are: Dynamic disks support multi-partition volumes; basic disks do not. Windows stores basic disk partition information in the registry and dynamic disk partition information on the disk Dynamic disks allow more flexible configuration without the need to restart the system. Some space at the end of the disk is reserved by the setup program of Windows with a kernel version of 5.x lest the disk would be upgraded to a dynamic one. The amount that is reserved is one cylinder or 1 MB, whichever is greater. One cylinder depending on drive geometry and translation can be up to 8 MB (to be precise, 512 bytes/sector × 63 sectors/head × 255 heads/cylinder = 8225280 bytes = 7.844 MiB) which account for a remaining 8 MB free space once Windows setup is used to create a partition. Coincidentally, Solaris 11 leaves exactly this amount of space at the beginning of a disk. Furthermore, this is not true since Windows Vista which always leaves 1 MB that is aligned to 2048 sector boundaries at the end of a local disk for the purpose of dynamic disk.
Compatibility problems
Disk Management in Windows Vista creates partitions according to a 1-MB alignment boundary, ignoring the previous conventions called "drive geometry" or "CHS". In other words, Vista's Disk Management acts like it is using a non-standard CHS geometry of 2048 sectors per track/head and 1 track/head per cylinder (the sectors being of so that 2048 sectors is ).
Compatibility problems with using a 1-MB alignment boundary
Extended partition tables that are edited with Disk Management in Windows Vista should not be edited with Disk Management in Windows XP, as it may delete these extended partitions without warning. One way to correct these mixed partition tables is to delete all partitions (reboot or reconnect drive) and use only one partition editor on the drive. Windows XP or Windows Server 2003 may not be installed to partitions created with Disk Management in Windows Vista. These alignments ignore prior CHS conventions such as the regular intervals at which partitions begin and end, and the distance between the extended boot records and their logical drives. Other operating systems, boot loaders, or partitioners may have problems viewing or editing partitions that do not follow a CHS alignment. (Generally, unpredictable results may come from using more than one partitioner on the same partition table without checking the alignments with tools such as Ranish Partition Manager. For example, operating system installers usually start with a partition editor so it may be important that this uses the same alignments as the previous partition editors, if all partitions are not deleted (and the computer reset) before installing the operating system. The variation in CHS geometry is almost always a different number of heads per cylinder, for example, 240 instead of 255. However, partition editors may seem to ignore this sort of geometry in some situations. "Head" and "track" mean the same thing in this context.)
Advantages of using a 1-MB alignment boundary
Microsoft states that on large-sector drives, also known as advanced format, there is a "performance issue" (i.e., problem) when the starting offset of the first partition is an "odd" number. This partition alignment offset also affects newer generation drives not necessarily specified as advanced format such as SSD drives. Misalignment causes severe degradation not only with random write performance, but also with sequential write performance (normally to a far lesser degree). The "starting offset" refers to the sectors before the partition. "3F" is a hexadecimal value; in decimal that is "63". This is the size of one head (or "track") in terms of a standard CHS geometry. The hex value "800", in decimal form is 2048, so this is referring to the first MB of space, from the start of the disk. Because a 1-MB alignment boundary is used by the Vista partitioner(s), is "reserved for" the Master boot record (MBR), instead of the traditional 63 sectors ( ). Note that the MBR is only one sector in size, but many software packages use these 63 sectors of "free space" (or any "free space" preceding the partition) for their purposes. 63 sectors is the minimum space that should be reserved for the MBR or an Extended Boot Record(EBR). What this means is that, if there were no partitions on a disk when it was booted, a partition was created using standard CHS geometry (as would be used by most partition editors such as DOS fdisk, Linux fdisk, Ranish Partition Manager, or an XP installation disk), and this partition was created at the start of the disk, then the partition will start on the 2nd head. The partition could not begin at the first sector because the MBR located there, so instead it starts the partition on the second head. When primary partitions are created anywhere else (following typical CHS geometry alignment) they start at the beginning of a cylinder. If a computer is booted with no partitions defined, and the first partition is created with the Vista installation disk, it will instead use the 1-MB alignment. (The partitioner on the Vista installation disk follows the 1-MB alignment just as Disk Management in Windows Vista does.) By following a 1-MB alignment, all partitions will have an even numbered offset (so long as no other partitioner is used on the drive). Using a 1-MB alignment boundary allows safer editing of the partition table with Disk Management in Windows Vista. Partition tables using a CHS geometry (or some mix of alignments) may prevent Vista from resizing partitions or it may produce unconventional partition tables. For example, the endings of the "EBR extended partitions" (type ) may overlap other partitions, and it will leave unprecedented amounts of space between an extended boot record and its logical drive. Ranish Partition Manager does not show an error if there are more than 63 sectors between the EBR and its logical volume, so long as the EBRs and VBRs are on the first sector of any track (head). If either the VBR or the EBR are not on the first sector of a head, Ranish Partition Manager shows the "partition" in red and when the partition is highlighted, this error message appears: "Boot sector doesn't have valid information". Using the 1-MB alignment boundary will not put VBRs or EBRs on the first sector of a track (according to any standard CHS geometry) and Disk Management in Windows Vista will not use the CHS geometry of a partition table created with a different partition editor. A disk that is solely partitioned with Disk Management in Windows Vista can create partitions in exact MB sizes and never leave leftover bits of space between partitions. (As long as the full allocated for each logical partition is not count to contain just a single sector extended boot record.) With Vista Disk Management in Windows Vista, all the logical drives besides the one nearest the beginning of the extended partition (type 0x0F), usually reserve exactly one additional MB, for an extended boot record, instead of the 63 sectors ( ) that is most commonly reserved according to alignments based on a CHS geometry. If other partition editors are used on the disk then Vista DM may reserve different amounts of space for the EBRs.
External links
Captive-NTFS Logical Disk Manager FAQ Comparison matrix of Windows LDM and Veritas Volume Manager libldm — LGPL library for reading Windows LDM on Linux
Text derived from https://en.wikipedia.org/w/index.php?oldid=1376164817 under CC BY-SA 4.0; modifications have been made.