You are correct, the "identical architecture" means the same machine
hardware name as shown by the -m option of the uname command.
Thanks,
Tru.
From: gpfsug-discuss-requ...@spectrumscale.org
To: gpfsug-discuss@spectrumscale.org
Date: 09/22/2020 05:18 AM
Subject:[EXTERNAL]
Hi Renar,
Let's see if it is really the /bin/rm is the problem here. Can you run the
command again without cleanup the temp files as follow:
DEBUG=1 keepTempFiles=1 mmgetstate -a
Thanks,
Tru.
From: gpfsug-discuss-requ...@spectrumscale.org
To: gpfsug-discuss@spectrumscale.org
Date:
Yes, you can use mmchconfig for that.
eg: mmchconfig sudoUser=gpfsadmin
Thanks,
Tru.
Message: 2
Date: Wed, 10 Oct 2018 15:58:51 +
From: Simon Thompson
To: "gpfsug-discuss@spectrumscale.org"
Subject: [gpfsug-discuss] Sudo wrappers
Message-ID:
Yes, older versions of GPFS don't recognize /dev/nvme*. So you would
need /var/mmfs/etc/nsddevices user exit. On newer GPFS versions, the nvme
devices are also generic. So, it is good that you are using the same NSD
sub-type.
Cheers,
Tru.
From: gpfsug-discuss-requ...@spectrumscale.org
1) That is correct. The grace period can't be set for per-fileset
quota. As you pointed out, you can only change the grace period for
user, group or fileset.
If you want a particular fileset to have no grace period, you can
set the hard limit to be the same as the soft limit.
When the grace
What you can do is create network alias to the old IP. Run mmchnode to
change hostname/IP for non-quorum nodes first. Make one (or more) of the
nodes you just change a quorum node. Change all of the quorum nodes that
still on old IPs to non-quorum. Then change IPs on them.
Thanks,
Tru.
The dates that have the zone abbreviation are from the scripts which use
the OS date command. The daemon has its own format. This inconsistency
has been address in 4.2.2.
From: gpfsug-discuss-requ...@spectrumscale.org
To: gpfsug-discuss@spectrumscale.org
Date: 09/02/2017 07:00 AM
The discrepancy between the mmlsconfig view and mmdiag has been fixed in
GFPS 4.2.3 version. Note, mmdiag reports the correct default value.
Tru.
From: gpfsug-discuss-requ...@spectrumscale.org
To: gpfsug-discuss@spectrumscale.org
Date: 09/01/2017 06:43 PM
Subject:
This sounds like a known problem that was fixed. If you don't have the
fix, have you checkout the around in the FAQ 2.4?
Tru.
From: gpfsug-discuss-requ...@spectrumscale.org
To: gpfsug-discuss@spectrumscale.org
Date: 08/02/2017 06:51 AM
Subject:gpfsug-discuss Digest, Vol 67,
