|
My understanding is you cannot have drives of a different type in the same raid set. Drive 1 can participate in a raid set, but is not stripped, therefor shows all of the available disk. If drive 1 was mirrored you would see two drives labeled as drive 1 and no drive 2. That was how our 510 was configured, drive 1 mirrored to drive 2, drives 3-18 in two raid sets, all in the system ASP. Under 4.x you can add the load source into a raid set. If I remember the original post correctly, the user just added three more drives. I also remember, but not sure, that you must have at least 4 drives to define a raid set and no more than 10 drive can be in one set. I would also add that a user ASP can overflow into the system ASP, but the system ASP canNOT overflow into a user ASP. I doubt that they have more than one ASP defined. Christopher K. Bipes Mailto:chrisb@cross-check.com Senior Programmer/Analyst Http://www.cross-check.com CrossCheck, Inc. 707 586-0551 x 1102 6119 State Farm Drive 707 586-1884 FAX Rohnert Park, CA 94928 ----- Original Message ----- From: <pytel@us.ibm.com> To: <MIDRANGE-L@midrange.com> Sent: Thursday, September 07, 2000 7:09 PM Subject: RE: WrkSysSts > Drive 1 is full size. Drives 2-5 have reduced sizes like they are in a RAID > set. I guess unit 1 is mirrored drive. We do not see mirrored pair, because it has the same unit number and WRKDSKSTS does not show it. > You cannot divide a RAID set between two ASP, can you? Yes, you can. This could explain sharp difference in %use and utilization. If these are two different ASPs then they are properly balanced (within themselves). Unit 1 is always somewhat more loaded than others. My guess this is an older system which could not have load source in a RAID set. So what we have is a 10 drive system. Two drives are mirrored. Other 8 drives are in two RAID sets. And drives 7, 8 and 9 could be ASP 2. Work with Disk Status Elapsed time: 00:06:02 Size % I/O Request Read Write Read Write % Unit Type (M) Used Rqs Size (K) Rqs Rqs (K) (K) Busy 1 6607 4194 99.9 7.3 8.9 5.4 1.8 7.3 13.6 5 2 6607 3145 99.9 3.3 12.6 1.7 1.6 20.0 5.1 2 3 6607 3145 99.9 2.8 14.6 1.6 1.2 19.3 8.4 2 4 6607 3145 99.9 3.6 11.7 1.9 1.7 16.5 6.1 3 5 6607 3145 99.9 4.2 11.0 1.8 2.3 18.7 4.8 1 6 6714 13161 99.1 6.6 11.5 4.4 2.1 13.3 7.7 6 7 6714 13161 38.8 4.7 19.1 1.2 3.4 27.3 16.2 2 8 6714 13161 38.8 4.3 18.7 1.9 2.3 21.8 16.2 2 9 6714 13161 38.8 4.2 20.6 1.5 2.6 26.7 17.1 2 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.