Hello,

maybe someone on the list can confirm my current observation...or just saves a 
bit of debugging time ;)

We are running GPFS 4.1.0.8 with CentOS 7.2.
With the recent update to systemd, GPFS is no longer started after a machine 
reboot.
I traced this back to systemd and the /etc/init.d/gpfs initscript.
systemd-sysv-generator no longer converts /etc/init.d/gpfs to a unit file, 
because it is a symlink pointing to /usr/lpp/mmfs/bin/gpfsrunlevel.
Replacing the symlink with a copy of the file works as a workaround and systemd 
starts GPFS again on boot time.

I am aware of the systemd always unmounting filesystems issue, which had been 
recently posted here as well.
But so far, I did not read about this particular issue.

Working on 7.1:
# systemctl status gpfs
gpfs.service - LSB: General Parallel File System
   Loaded: loaded (/etc/rc.d/init.d/gpfs)

Broken on 7.2:
# systemctl status gpfs
● gpfs.service
   Loaded: not-found (Reason: No such file or directory)

As this my first post to this mailing list, a brief introduction.
We (DESY) are running a GPFS installation with ESS building blocks as a storage 
system for our local x-ray light source.
Currently we are in shutdown phase, where we prepare everything for the next 
run of the accelerator with bigger and faster detectors.
Martin Gasthuber recently held a talk about our setup on the GPFSUG at SC15 as 
well.

Regards,
Stefan
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to