×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
So, even if they started out with a three drive raid set, it only put the
raid striping on 2 of the three drives? Odd. Then again, so is a three
drive raid set. The math almost makes sense. Take one drive (17gb) out
for raid striping. Divide that by 2 is roughly 8.5. So that would make
two drives look like roughly 8gb drives. Yep, as another poster
suggested, we need the drive type of these drives from WRKDSKSTS. Even
better would be both the "type" and the "model" from STRSST, 3. Work with
disk units, 1. Display disk configuration, 1. Display disk configuration
status.
If this is the case, then removing RAID from all of these drives and
turning it back on thus putting the stripe across ALL drives might really
increase performance.
You could still chop them up into alternate ASP's if you wanted to. Even
if they are all in the same raid set. I'm not a big fan of that though.
Mainly because islands of disk is more management. Let's see, where do I
put this new library? ASP x or y? Which is logical? Which has the
space?
And, unless you have lots of drives, on different controllers, and you
want to keep receivers on a different set of arms than on your DB arms, I
can't see any perform increase by multiple ASPs. And, it's not like this
old AS/400 with teeny tiny disks is concerned about keeping new SSD's in
their own ASP to segregate data which requires high read performance.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Removing (unconfigured) disks from RAID-5 array?, (continued)
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.