Many responses here are about the meta stripe size. For a long time the meta stripe has not been adjustable. When it was adjustable it was always in increments of cylinders. You should assume that this is not adjustable unless you have a very old Symm and SE version.
The RAID stripe size on DMX and VMAX 20k are all 256K. For the 40K and the new 10K it is 128K for 7+1 and RAID6. 3+1 is still 256k. It is not adjustable.
The VP stripe is 768k across the TDATs in a VP environment. This is also not adjustable.
I'm not sure where you got that table you posted from, but it is incorrect. The DMX1-4 all have 4 tracks for the RAID stripe per disk. The DMX1-2 have a 32k track and DMX3 and above all have 64k tracks. There has been a recent change on the VMAX 40K and the new VMAX 10K where some RAID options went from 4 tracks to 2 tracks to better line up with the VP stripe.
Also I didn't mention that since the meta stripe was made a fixed size, it has always been 960k. On DMX1-2 that was 2 cylinders, and on DMX3 and above it was 1 cylinder since the track size doubled.
So how will data actually be written in the end? I assume FAST VP chunks have priority over the stripe size, but assumption is the mother of all... you know.
Archuperi721
110 Posts
1659
0
Posted December 20th, 2012 02:00
The detailed output of symmetrix device will give you the stripe size information.
Symmetrix stripe size is not at 256 KB. Here, everything is calculated based on the cylinder.
e.g.
Meta Configuration : Striped
Meta Stripe Size : 960k (1 Cylinders)
Meta Device Members (4) :
Symdev –sid xxxx show xxxx
Or symdev –sid xxxx list -meta
Regards,
Periyakaruppan N (Peri),