On 07/15/2020 10:00 PM, Lew Wolfgang wrote:
I still haven't gotten a confirmation about where/how to update the firmware in this case. It's Broadcom controller modified by SuperMicro.
But in any case, in chasing down issues with methods suggested by Anthony Iliopoulos (Kernel Team) I discovered that the RAID volumes in question, when they were created with the Broadcom GUI, a parameter for stripe size was increased beyond the suggested default. This change created the I/O size clash that was flagged by the Leap 15.2 XFS kernel module. I deleted the two volumes, and re-created them without changing the defaults, and all is well!
Left as a problem for the near future is that we'll probably see this again when upgrading existing 15.1 servers, but at least we'll be prepared for the unpleasantness and be able to take appropriate action.
Interesting. I never get to play with large number of spares or large arrays above the normal little-office world of 1-3T, but did try and keep the chunk, stride and stripe of the arrays optimized for the arrays I was messing with: Chunks: the hidden key to RAID performance http://www.zdnet.com/article/chunks-the-hidden-key-to-raid-performance/ and Calculating the stride and stripe width https://wiki.archlinux.org/index.php/RAID#Calculating_the_stride_and_stripe_... So what you ran into was an issue setting the stripe too large via the Broadcom Gui when adding the filesystem to your array? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org