Thank you for the reminder. I’ve received that nasty surprise myself, but just
long ago enough to have forgotten it. Would love to see that fixed.
> On Jan 16, 2020, at 10:32 AM, Skylar Thompson wrote:
>
> Another problem we've run into with automating GPFS installs/upgrades is
> that the
On Spectrum Scale 4.2.3.15 or later and 5.0.2.2 or later, you can install
gplbin without stopping GPFS by using the following step:
Build gpfs.gplbin using mmbuildgpl --build-packge
Set environment variable MM_INSTALL_ONLY to 1 before install gpfs.gplbin
package with rpm -i gpfs.gplbin*.rpm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Felipe,
I either misunderstood support or convinced them to take further
action. It at first looked like they were suggesting "mmbuildgpl fixed
it: case closed" (I know they wanted to close the SalesForce case
anyway, which would prevent
We actually add an ExecStartPre directive override (e.g.
/etc/systemd/system/gpfs.service.d/gpfs.service.conf) to the gpfs.service
[Service] section that points to a simple script that does a check of the GPFS
RPMs installed on the system and updates them to what our config management
Another problem we've run into with automating GPFS installs/upgrades is
that the gplbin (kernel module) packages have a post-install script that
will unmount the filesystem *even if the package isn't for the running
kernel*. We needed to write some custom reporting in our configuration
management
Hi Ryan,
I'm aware of this ticket, and I understand that there has been active communication with the service team on this problem.
The crash itself, as you indicate, looks like a problem that has been fixed:
Hello,
as requested:
* gpfsug-discuss-requ...@spectrumscale.org
[15.01.20 13:40]:
> Please introduce yourself to the members with your first post.
I'm Philipp from Berlin, Germany. The IT department of the "Freie
Universität Berlin" is working place.
We have a DDN-System with some PB of
