[gpfsug-discuss] ESS and Disk Paths

[Alec.Effrat at wellsfargo.com]

Fine.. challenge accepted

awk '/disk/&&!/RAID/{print; l++} END {printf "%0.2f\n", l/2}'

$ ( echo "disk123"; echo disk234; echo disk897; echo "RAID") | awk '/disk/&&!/RAID/{print; l++} END {printf "%0.2f\n",l/2}'
disk123
disk234
disk897
1.50

-----Original Message-----
From: gpfsug-discuss <gpfsug-discuss-bounces at gpfsug.org> On Behalf Of Jonathan Buzzard
Sent: Tuesday, May 10, 2022 3:09 PM
To: gpfsug-discuss at gpfsug.org
Subject: Re: [gpfsug-discuss] ESS and Disk Paths

On 10/05/2022 20:57, Wahl, Edward wrote:

> There is much you can do with 'lsscsi' and "mmlspdisk" and whatnot.
>   Or something like "mmgetpdisktopology  >
> /tmp/mmgetpdisktopology.out; topsummary /tmp/mmgetpdisktopology.out   > topsummary"
>
> mmlspdisk should all 4 paths with 2 being notenabled.  Look for
> missing paths?  This may be the fastest.
> " device =
> "//ibmgssio5-hs.ten/dev/sdo(notEnabled),//ibmgssio5-hs.ten/dev/sdfe(notEnabled),//ibmgssio6-hs.ten/dev/sdo,//ibmgssio6-hs.ten/dev/sdfe"  > "

On a DSS-G you can hop onto one of the servers and do

lsscsi | grep disk | grep -v RAID | awk 'END {print NR/2}'

The number should be the number of disks that you have including the log tip drives. If it's not then there is a path issue. I would imagine it's the same on the ESS.

If I thought about it for a bit you could ditch the two greps and do it all in Awk. If the Awk is too complicated just replace it with 'wc -l'
but you will end up with a number that should be twice the number of drives.


JAB.

--
Jonathan A. Buzzard                         Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
https://urldefense.com/v3/__http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org__;!!F9svGWnIaVPGSwU!sl4vQf2qHT1fXJuzhho-JRymyZj12LRJ9FWZDM8-GQevtCoEp6PLOLnqSa5n94u0nmRXL0WEncaSGiYck_o6XaO3xk5vf4OpaJ3ChQ$

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20220510/a6d1281e/attachment.htm>