Panics on mps(4) firmware timeouts

Correct.

Hi, im using an LSI HBA too. Form 12.0-U1 on my backups to a LTO-VI Library went smooth without shoeshining becaus of the increased io_size.

After the update to U2 my backups failed, because of the default io_size. I had no problems with my attached 16x8TB seagate Exos SAS-Drives.

Just to be sure, if i want to increase the io_size to 256k, i set the tunable to 64 ? Is that correct ?

So I've been up for another 5-ish days, no errors or freakouts. So I guess that's good

> We found one bug that the tunable isn't happening when a comment is included.

Please create separate ticket for us to look at that another day.

> But, why did my panics go away when the tunable was set to a higher number anyway?

Was it happening just after boot before?  Can't it be that it happen only later when memory fragmentation starts to grow, making addressation more complicated for HBA?  Or may be it is specific to some specific I/O pattern, like scrub, that completed meanwhile.  I can speculate all day long.

Here's the drive information that I've got in the system:

Script used to get you this info:

output: