freebsd-nq/uts
Alexander Motin 843b26d023 8961 SPA load/import should tell us why it failed
illumos/illumos-gate@3ee8c80c74

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()`.

Reviewed by: George Wilson <george.wilson@delphix.com>
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed by: Andrew Stormont <andyjstormont@gmail.com>
Approved by: Dan McDonald <danmcd@joyent.com>
Author: Pavel Zakharov <pavel.zakharov@delphix.com>
2018-02-21 23:42:30 +00:00
..
common 8961 SPA load/import should tell us why it failed 2018-02-21 23:42:30 +00:00
intel Import fasttrap_isa.c from OpenSolaris. 2010-07-06 10:22:17 +00:00
sparc 5045 use atomic_{inc,dec}_* instead of atomic_add_* 2014-08-20 06:22:59 +00:00