On 07/16/2020 12:32 AM, Lew Wolfgang wrote:
Right, but I had no idea what the correct parameters should be!
Going forward. we have multiple RAID controller model numbers, with different RAID volume and disk types. Then, how do those numbers translate to the sunit and swidth metadata parameters? It might be safer to start from scratch and let the RAID controller do its thing, correctly this time. I'll have a 10-gigE link to back them up with, so it might not be too bad.
That's where those two links I provided can help. You will have to figure out what the Broadcom uses for 'chunk' size, but then you can use: stride = chunk size / block size stripe width = number of data disks * stride You will have to check, but it looks like your sunit is stride and the swidth is stripe. I have a couple of LSI Megaraid cards 8-port. The gui (if you can call it that) was always fairly easy to deal with. IIRC it used values that were inline with what mdadm did for RAID1. I always hated having to mess with well-working file systems. Even replacing failed disks in the arrays, even though very simple, always left you with that feeling of "what it this blows up?". Thankfully it hasn't yet, but that doesn't do away with that feeling altogether :) -- 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