Disk partition
A disk partition is a contiguous range of logical blocks on a block device, described by a partitioning scheme.
A partition table records the division into address ranges. The range is not itself a filesystem: partitioning and organizing files are separate layers. [1]
GPT entries store an inclusive StartingLBA and EndingLBA. The byte offset is StartingLBA times logical-block bytes, and the length is (EndingLBA - StartingLBA + 1) times logical-block bytes. Physical-sector size is not the multiplier for these addresses. [2]
Resizing a partition and resizing its filesystem are distinct operations. For ext2/3/4, resize2fs changes the filesystem, not the partition table. Growing the containing range does not by itself make that space usable by the filesystem; shrinking it below the filesystem size can destroy data. [3]
A readable partition table does not establish that the enclosed filesystem or files are intact. Interpreting GPT LBA ranges in an image requires the logical-block size used by that layout. Check the acquired bytes and their interpretation separately. [4]
Unit trap: blockdev --report labels its partition start in 512-byte sectors; --getsz uses the same fixed unit. Neither count changes to 4096-byte units when --getss reports a 4096-byte logical sector. [5]
Relations
- related
- GUID Partition Table (GPT), Block device, Filesystem, Logical sector, Logical volume, Partition alignment
Citations
- util-linux v2.40.4: fdisk, partition tables and block devices
- UEFI 2.10, section 5.3.3: GPT partition entry ranges
- e2fsprogs v1.47.2: resize2fs, separate filesystem and partition resizing
- Hesela: acquisition coverage and GPT metadata checks
- util-linux v2.40.4: blockdev report and sector-size units
Sources & caveats
- Documentation synthesis using UEFI 2.10, util-linux v2.40.4 and e2fsprogs v1.47.2; no device repartitioning or recovery experiment.
- Contiguity describes the partition's logical address range, not placement on physical media or a volume manager's backing extents.