Really it depends on the host application you are running, but generally speaking it's not a good idea to run a stripe on top of a stripe. If you want to do host striping on meta volumes, you can, but it's best to uses a concatenated meta volume rather than a striped one. But also consider if you're using thin devices. Thin devices are already striped on the back-end, so you usually are fine using concatenated meta devices (but not always, depending on performance requirements)..
Also keep in mind SRDF limitations.. If you're running SRDF/Sync you'll need to uses striped luns as to avoid a performance problem where-by you have limited write concurrency..
Out of curiosity, why are you looking at host striping?
Zhang, the main reasoning behind this would be to avoid potential performance degradation depending on the config and of course the workload. Your Data is already striped at the RAID level, also at the pool (if using TDEV), if you are using a stiped meta then you are already at 3 layers of striping going deeper is generally not recommended.
cincystorage
2 Intern
•
467 Posts
1710
0
Posted November 20th, 2013 18:00
Really it depends on the host application you are running, but generally speaking it's not a good idea to run a stripe on top of a stripe. If you want to do host striping on meta volumes, you can, but it's best to uses a concatenated meta volume rather than a striped one. But also consider if you're using thin devices. Thin devices are already striped on the back-end, so you usually are fine using concatenated meta devices (but not always, depending on performance requirements)..
Also keep in mind SRDF limitations.. If you're running SRDF/Sync you'll need to uses striped luns as to avoid a performance problem where-by you have limited write concurrency..
Out of curiosity, why are you looking at host striping?