: Is this a Compressed RAR file (like 326.rar ) containing software, game mods, or documents that you need help opening or explaining?
: Could it be a part number, a specific error code, or a reference to a product (like a radio or machine part)? An online handle or brand :
Could you tell me you’re looking for (e.g., a summary, instructions, or a creative post) and where you encountered the term ?
326rar
: Is this a Compressed RAR file (like 326.rar ) containing software, game mods, or documents that you need help opening or explaining?
: Could it be a part number, a specific error code, or a reference to a product (like a radio or machine part)? An online handle or brand : 326rar
Could you tell me you’re looking for (e.g., a summary, instructions, or a creative post) and where you encountered the term ? : Is this a Compressed RAR file (like 326
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.