I/O to pool appears to be hung, panic !

[Ben RUBSON]

> On 29 Jun 2017, at 20:40, Karli Sjöberg <karli at inparadise.se> wrote:
> 
>> Den 29 juni 2017 3:37 em skrev Ben RUBSON <ben.rubson at gmail.com>:
>> 
>> I also tried to look for some LSI SAS2008 error counters (on target side),
>> but did not found anything interesting.
>> (sysctl -a | grep -i mps)
> 
> Here's a well kept secret I got from LSI once:
> 
> /boot/loader.conf:
> dev.mps.0.debug_level="0x1F"


Thank you Karli for this tip !
I just noticed this is explained in MPS(4), DEBUGGING section.
0x1F is then :
0x0001 Enable informational prints (set by default).
0x0002 Enable prints for driver faults (set by default).
0x0004 Enable prints for controller events.
0x0008 Enable prints for controller logging.
0x0010 Enable prints for tracing recovery operations.

Controller events are however extremely verbose.
Perhaps 0x1B is then slightly better.

Here is a useful link to "decode" logged messages :
http://blog.disksurvey.org/blog/2014/08/10/decoding-lsi-loginfo-codes/

Ben