sfdisk: add hint about duplicate UUIDs when use dump

Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=2215082 Upstream: http://github.com/util-linux/util-linux/commit/60c81b3272d03959dfee465f1ecaf40ba3e70cb3 Signed-off-by: Karel Zak <[email protected]>
redhat-plumbers · Aug 24, 2023 · 2ab525d · 2ab525d
1 parent 71e5eb4
commit 2ab525d
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/disk-utils/sfdisk.8.adoc b/disk-utils/sfdisk.8.adoc
@@ -342,6 +342,8 @@ creates empty GPT partition table. Note that the *--append* disables this featur
 
 It is recommended to save the layout of your devices. *sfdisk* supports two ways.
 
+=== Dump in sfdisk compatible format
+
 Use the *--dump* option to save a description of the device layout to a text file. The dump format is suitable for later *sfdisk* input. For example:
 
 ____
@@ -354,6 +356,10 @@ ____
 *sfdisk /dev/sda < sda.dump*
 ____
 
+Note that sfdisk completely restores partition types and partition UUIDs. This could potentially become problematic if you duplicate the same layout to different disks, as it may result in duplicate UUIDs within your system.
+
+=== Full binary backup
+
 If you want to do a full (binary) backup of all sectors where the partition table is stored, then use the *--backup* option. It writes the sectors to _~/sfdisk-<device>-<offset>.bak_ files. The default name of the backup file can be changed with the *--backup-file* option. The backup files contain only raw data from the _device_. Note that the same concept of backup files is used by *wipefs*(8). For example:
 
 ____