DDF is the SNIA standard for describing RAID sets on disk, so that different controllers and software can read one another’s arrays. It is used by some Linux MD arrays and by several firmware and controller vendors.
Overview
DDF stores an anchor header near the end of each member disk with signature 0xDE11DE11, followed by controller data, a physical disk records table, virtual disk records and configuration records. Virtual disks describe the RAID level, stripe size, member order and extents. All values are big-endian.
History
Published by the Storage Networking Industry Association (SNIA) in 2006.
Structures
Offsets are in bytes from the start of the structure named in each heading. Field names are descriptive and are not an official specification. Fixed-width integers are shown as u/i (unsigned/signed) followed by bit width and byte order.
Read Sectors
Offset
Size
Type
Field
Notes
at
2
u16 BE
–
at
4
u32 BE
–
at
8
u64 BE
–
Other fields read
Read in
Offset
Size
Type
Field
Notes
Crc Ok
0x4
4
u32 BE
Stored
Constants
Ddf Module
Name
Value
Type
Notes
HeaderMagic
0xDE11DE11
uint
PhysicalRecordsMagic
0x22222222
uint
DiskDataMagic
0x33333333
uint
VirtualRecordsMagic
0xDDDDDDDD
uint
ConfigMagic
0xEEEEEEEE
uint
GuidLength
24
int
Members in order: each mirror set’s disks in turn for RAID 10.
Name
Value
Type
Notes
sectorSize
512
int
DDF addresses in 512-byte blocks (as mdadm reads it)
Sector
512
int
Structures and constants were extracted from the implementation. Prose sections are a summary from public sources; verify details before relying on them.