MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » September 2012

Re: Unload/Reload



fixed

My boss wants to replace the four 4327-074's with 4329's (281GB's instead
of 70GB's).

Wellll that's gonna be a problem. You see the 074s are the ones that contain the RAID stripe so when you pull those the 070's will be unprotected. Then you'll have to re-start RAID on them after you format them and you'll get four of the 070s to step up and become replacement 074's. :-)

So no matter what yer doin' you will be removing four 070s for a total of 282GB removed from the ASP. By my math, when you do that you will have 26GB of stuff laying on the floor. In other words if you did try to remove four of the 070s concurrently the system would stop you from trying. If you could get rid of another 50GB of stuff (or so for a cushion) temporarily this could all be done with NO downtime (assuming i 7.1).

Select four drives that are 070s.
STRASPBAL and drain them to near zero.
Use SST to remove them concurrently from the system.
Use SST to exclude them from RAID.
Use SST to concurrently remove them.
Use SST to concurrently install the new disks.
Use SST to Initialize and format the new disks.
Use SST to start RAID on the new disks. (Will take only seconds if you did previous step)
Use SST to add AND BALANCE them to the ASP.

Don't forget to put the 50GB of stuff back.

Also it has been my experience that having drives of THREE different sizes (or worse) is poor for performance. You would have 70/140/280 and thus the 280s will work twice as hard as the 140s and four times as hard as the 70s. Rather than 280s I would do 140s until all 70s were gone, then go to 280s in the future if needed.

- Larry "DrFranken" Bolhuis.

By my math you

On 9/4/2012 10:27 AM, rob@xxxxxxxxx wrote:
This lpar's pretty tight on disk, let me scratch that. That's an
"opinion". Let me throw out numbers.

Size %
Unit Type (M) Used
1 4328 141129 81.3
2 4328 105847 81.3
3 4328 105847 81.3
4 4328 105847 81.3
5 4328 105847 81.3
6 4328 141129 81.3
7 4327 52923 86.2
8 4327 52923 86.2
9 4327 52923 86.2
10 4327 52923 86.1
11 4328 141129 81.3
12 4327 70564 86.2
13 4327 70564 86.2
14 4327 70564 86.2
15 4327 70564 86.2
16 4327 70564 86.2
17 4327 70564 86.2
18 4327 70564 86.2

Parity Resource
Set ASP Unit Type Model Name Status
1 571F 001 DC05 RAID 5
1 17 4327 070 DD016 Active
1 16 4327 070 DD017 Active
1 15 4327 070 DD015 Active
1 14 4327 070 DD014 Active
1 12 4327 070 DD013 Active
1 13 4327 070 DD012 Active
1 18 4327 070 DD018 Active
1 10 4327 074 DD010 Active
1 9 4327 074 DD009 Active
1 8 4327 074 DD008 Active
1 7 4327 074 DD007 Active
2 571F 001 DC05 RAID 5
1 2 4328 074 DD006 Active
1 3 4328 074 DD005 Active
1 4 4328 074 DD001 Active
1 5 4328 074 DD002 Active
1 6 4328 070 DD003 Active
1 1 4328 070 DD004 Active
1 11 4328 070 DD011 Active

My boss wants to replace the four 4327-074's with 4329's (281GB's instead
of 70GB's).

Physical location:
Unit ID. . . . . . . . . . : U5787.001.DQD0C25
Planar ID. . . . . . . . . : P2
Device . . . . . . . . . . : D7-D10

All attached via:
Resource Type-model Status Text
CMB05 571F-001 Operational Storage Controller
DC05 571F-001 Operational Storage Controller
Location : U5790.001.13359A2-P1-C1


Rob Berendt






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact