Hi
If you are doing it offline (which for bigger setups) and pass the class or CSV
of nodes, it is done in parallel in all nodes.
For your request I think there is a RFE (not sure public or not) already
created, but I don’t disagree would be nice improvement to lock at the single BB
--
Ystävällisin terveisin/Regards/Saludos/Salutations/Salutacions
Luis Bolinches
Executive IT Specialist
IBM Storage Scale development
Phone: +358503112585
Ab IBM Finland Oy
Toinen linja 7
00530 Helsinki
Uusimaa - Finland
Visitors entrance: Siltasaarenkatu 22
"If you always give you will always have" -- Anonymous
https://www.credly.com/users/luis-bolinches/badges
-----Original Message-----
From: gpfsug-discuss <[email protected]> On Behalf Of
Hannappel, Juergen
Sent: Tuesday, 27 June 2023 19.07
To: gpfsug main discussion list <[email protected]>
Subject: [EXTERNAL] [gpfsug-discuss] Why cluster-wide locks for
firmware-updates and the like
Moin,
when e.g doing mmchfirmware there is a cluster-wide lock preventing me from
running mmchfirmware on several building blocks at once, while I would assume
that only within one building block a lock is needed.
Why is that so? Can that be changed in a future release?
Also some apparently cluster wide locks create false alarms when checking for
the recovery group status on one building block is blocked by some actions on
another one...
--
Dr. Jürgen Hannappel DESY/IT Tel. : +49 40 8998-4616
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
Unless otherwise stated above:
Oy IBM Finland Ab
PL 265, 00101 Helsinki, Finland
Business ID, Y-tunnus: 0195876-3
Registered in Finland
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
