Thanks, Johan.
Original Message:
Sent: Tue April 21, 2026 02:47 AM
From: Johan van Arendonk
Subject: Best practices for MDisk count/layout with FlashSystem as SVC backend
Sergio,
As far as I know, there are no specific recommendations regarding the number of mdisks per pool (except that there is a restriction on the maximum number of mdisks per pool).
Personally, I would use more than 1 in this case. You could also consider using childpools.
------------------------------
Johanvan Arendonk
------------------------------
Original Message:
Sent: Tue April 21, 2026 02:18 AM
From: SERGIO PARDOS
Subject: Best practices for MDisk count/layout with FlashSystem as SVC backend
Thanks, Johanvan
I assume the guidance above applies to the FlashSystem side. Now, once those (ie) 32 volumes are created and mapped to the SVC, let's assume I need to have several pools for organizational purposes... is there any specific guidance in regard of the number of managed disks I assign to each one of these mdiskgroups?
Thanks again and best regards.
------------------------------
SERGIO PARDOS
Original Message:
Sent: Tue April 21, 2026 02:07 AM
From: Johan van Arendonk
Subject: Best practices for MDisk count/layout with FlashSystem as SVC backend
Hello Sergio,
Have a look at Performance and Best Practices Guide for IBM Storage FlashSystem and IBM SAN Volume Controller
Chapter 3.4.4
For all-flash solutions, create 32 volumes from the available pool capacity, which can be reduced to 16 or even 8 for small arrays (for example, if you have 16 or fewer flash drives in a back-end pool).
For FCM arrays, the number of volumes is also governed by load distribution. 32 volumes out of a pool with an FCM array is recommended.
------------------------------
Johanvan Arendonk