First, have you looked at the sizes of the drives in WRKDSKSTS? Due to
differences in how RAID was done, they could all be different sizes that add
up to you're seeing.
No it does not include hot spare, it should show up as an unallocated drive,
or not at all. I suspect the hot spare is not quite set up right.
I do not believe the symlnk would affect the total storage, that's not where
the number is coming from, those stats are coming from the RAID card into
storage management.
Does the information in SST match up with what you are seeing in WRKDSKSTS?
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt
Olson
Sent: Thursday, May 03, 2018 1:49 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: WRKDSKSTS and finding true disk space usage
Does anyone know why WRKDSKSTS shows total ASP size as 1395GB when it should
really be around 1268?
We have 11 x 127GB drives in RAID 5 which should equal about 1268. We also
have one hot spare, bringing it to 1395.
Why would WRKDSKSTS show the hotspare as usable drive space??
Additionally, the percentage ASP used is off as well because of this.
Lastly, does the system incorrectly calculate total used disk space because
of the recursive sym link in QOpenSYs that links back upon itself up to a
depth of 10 times (therefore inflating QOpenSys consumed space by 10x)?
Thanks!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
