The devid is there to map disk device to physical device, in case of "unknown" devid, it is clear that we will not have the device path either, therefore the whole discussion about updating the parser is just meaningless.
Moreover, the only real use for devid and physical path for us is in case of boot pool, because our kernel is unable to discover disk devices on its own. In case of data pool, the devid/physical path can only be used to reduce the need to scan all disks, but only when the devid/path is known to us and is actually pointing to the correct device. If the devid/path is not known or if they do point to wrong device (the disk was moved to different host or controller), we must ignore the values, scan the disks to discover the pool components and update the pool label with correct information (unless the pool is imported read-only). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/605#issuecomment-383531172 ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/discussions/T33087f87f64e654e-Mcf2f71901c72029b8c26d797 Delivery options: https://openzfs.topicbox.com/groups
