Following up to my own problem…. It would appear mmsdrrestore doesn’t work (well) with quorum nodes in a CCR enabled cluster. So:
change node to non-quorum mmsdrrestore change back to quorum Hey IBM – how about we document this! Bob Oesterlin Sr Storage Engineer, Nuance HPC Grid From: <[email protected]<mailto:[email protected]>> on behalf of Robert Oesterlin <[email protected]<mailto:[email protected]>> Reply-To: gpfsug main discussion list <[email protected]<mailto:[email protected]>> Date: Thursday, April 14, 2016 at 2:39 PM To: gpfsug main discussion list <[email protected]<mailto:[email protected]>> Subject: Re: [gpfsug-discuss] CCR error messages after mmsdrrestore Yea – turning of CCR means shutting down the entire cluster. Not an option. CCR is VERY POORLY documented. Bob Oesterlin Sr Storage Engineer, Nuance HPC Grid From: <[email protected]<mailto:[email protected]>> on behalf of Jan-Frode Myklebust <[email protected]<mailto:[email protected]>> Reply-To: gpfsug main discussion list <[email protected]<mailto:[email protected]>> Date: Thursday, April 14, 2016 at 2:33 PM To: gpfsug main discussion list <[email protected]<mailto:[email protected]>> Subject: Re: [gpfsug-discuss] CCR error messages after mmsdrrestore I would try switching from CCR to primary/secondary config servers, maybe delete the paxos files, and then back to CCR. I believe that's how I got out of a similar situation on a v4.1.1.x installation this january..
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
