| Blogs | Classifieds | Downloads | FlashChat | Gallery | Googlemap | Invite Friends | Links | Projects | Reviews | Wiki |
| |||||||||
Welcome to the pSeries Tech Forums,
our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software. You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments. Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community. Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
| Our Sponsors | |
| | |
| Want to advertise? | |
![]() |
| | LinkBack | Thread Tools |
|
#1
| ||||
| ||||
Hi, i know this is an pSeries forum but given that an UNIX admin always has to do with many enviroments. My customer has an IBM SAN Volume Controller with some storage boxes connected, let's say an IBM DS8100 and a new DS8300. We have defined some volumes in the DS8300 of 1.6 TB and created some Mdiskgroups in the SVC with one of such big volumes as one whole mdisk. My question: what's the best practice for creating such volumes ?? is it better to create small volumes and small mdisk and assign them to many mdiskgroups or just create big volumes as the sample below ?? Another question: What's the meaning of the extend size in the mdisk ?? we have a extend of 16mb. Is this the best size from performance point of view ??. Thanks in advanced
__________________ cd3lgad0p |
|
#2
| ||||
| ||||
The best way to this, especially if the storage device is new is to use the largest LUNs and fewest managed disk groups are possible. Create your virtual disks across all of the managed disks in the managed disk group. This spreads the IO of the virtual disks across the greatest number of physical spindles, reducing the change of I/O contention and host disks.
__________________ $ PATH=pretending!/usr/ucb/which sense no sense in pretending! |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |