Check out “unmountOnDiskFail” config parameter perhaps? https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_tuningguide.htm
unmountOnDiskFail The unmountOnDiskFail specifies how the GPFS daemon responds when a disk failure is detected. The valid values of this parameter are yes, no, and meta. The default value is no. I have it set to “meta” which prevents the file system from unmounting if an NSD fails and the metadata is still available. I have 2 replicas of metadata and one data. Bob Oesterlin Sr Principal Storage Engineer, Nuance From: <gpfsug-discuss-boun...@spectrumscale.org> on behalf of "Buterbaugh, Kevin L" <kevin.buterba...@vanderbilt.edu> Reply-To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org> Date: Thursday, February 8, 2018 at 10:15 AM To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org> Subject: [EXTERNAL] [gpfsug-discuss] mmchdisk suspend / stop So … what I was wondering if I could do is to use mmchdisk to either suspend or (preferably) stop those NSDs, do the firmware upgrade, and resume the NSDs? The problem I see is that suspend doesn’t stop I/O, it only prevents the allocation of new blocks … so, in theory, if a user suddenly decided to start using a file they hadn’t needed for 3 months then I’ve got a problem. Stopping all I/O to the disks is what I really want to do. However, according to the mmchdisk man page stop cannot be used on a filesystem with replication set to one.
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
