From daafae4a1e6baf2bedbe30d591847aa4b2cbed81 Mon Sep 17 00:00:00 2001 From: Rich Ercolani <214141+rincebrain@users.noreply.github.com> Date: Sun, 19 Jun 2022 08:52:15 -0400 Subject: [PATCH] Additional caveats for by-XXX paths (#301) Added a few caveats I've run into about /dev/disk/ paths that weren't already present. Co-authored-by: George Melikov --- docs/Project and Community/FAQ.rst | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/docs/Project and Community/FAQ.rst b/docs/Project and Community/FAQ.rst index 3f6e660..fe95803 100644 --- a/docs/Project and Community/FAQ.rst +++ b/docs/Project and Community/FAQ.rst @@ -161,7 +161,9 @@ you. back anywhere in the system and your pool will still be automatically imported correctly. - Drawbacks: Configuring redundancy groups based on physical - location becomes difficult and error prone. + location becomes difficult and error prone. Unreliable on many + personal virtual machine setups because the software does not + generate persistent unique names by default. - Example: ``zpool create tank scsi-SATA_Hitachi_HTS7220071201DP1D10DGG6HMRP`` @@ -208,6 +210,21 @@ you. may apply depending on the naming method employed. - Example: ``zpool create tank mirror A1 B1 mirror A2 B2`` +- **/dev/disk/by-uuid/:** Not a great option + + - Summary: One might think from the use of "UUID" that this would + be an ideal option - however, in practice, this ends up listing + one device per **pool** ID, which is not very useful for importing + pools with multiple disks. + +- **/dev/disk/by-partuuid/**/**by-partlabel:** Works only for existing partitions + + - Summary: partition UUID is generated on it's creation, so usage is limited + - Drawbacks: you can't refer to a partition unique ID on + an unpartitioned disk for ``zpool replace``/``add``/``attach``, + and you can't find failed disk easily without a mapping written + down ahead of time. + Setting up the /etc/zfs/vdev_id.conf file -----------------------------------------