SPA load/import should tell us why it failed
When we fail to open or import a storage pool, we typically don't get any
additional diagnostic information, just "no pool found" or "can not import".
While there may be no additional user-consumable information, we should at
least make this situation easier to debug/diagnose for developers and support.
For example, we could start by using `zfs_dbgmsg()` to log each thing that we
try when importing, and which things failed. E.g. "tried uberblock of txg X
from label Y of device Z". Also, we could log each of the stages that we go
through in `spa_load_impl()`.
Updated by Electric Monk almost 4 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit 3ee8c80c747c4aa3f83351a6920f30c411236e1b Author: Pavel Zakharov <email@example.com> Date: 2018-02-06T17:36:45.000Z 8961 SPA load/import should tell us why it failed Reviewed by: George Wilson <firstname.lastname@example.org> Reviewed by: Matthew Ahrens <email@example.com> Reviewed by: Andrew Stormont <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>