In version 4.2.3 you can turn on QOS --fine-stats and --pid-stats and get
IO operations statistics for each active process on each node.
https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_mmchqos.htm
https://www.ibm.com/support/knowledgecenter/STXKQY_
Regarding mmbackup and TSM INCLUDE/EXCLUDE, I found this doc by
googling...
http://www-01.ibm.com/support/docview.wss?uid=swg21699569
Which says, among other things and includes many ifs,and,buts : "...
include and exclude options are interpreted differently by the IBM
Spectrum Scale mmbackup
Hi Sven,
we are seeing FileBlockRandomReadFetchHandlerThread.
I'll let you know once I have more results
Thanks,
Andreas
On 05/30/2017 03:55 PM, Sven Oehme wrote:
Hi,
the very first thing to do would be to do a mmfsadm dump iohist instead
of mmdiag --iohist o
Hi,
the very first thing to do would be to do a mmfsadm dump iohist instead of
mmdiag --iohist one time (we actually add this info in next release to
mmdiag --iohist) to see if the thread type will reveal something :
07:25:53.578522 Wdata1:20260249600 8192 35.930488076
18
Hi Andreas,
I often start with an lsof to see who has files open on the troubled filesystem
and then start stracing the various processes to see which is responsible. It
ought to be a process blocked in uninterruptible sleep and ideally would be
obvious but on a shared machine it might not be.
Hi John,
iotop wasn't helpful. It seems to be overwhelmed by what is going on on
the machine.
Cheers,
Andreas
On 05/30/2017 02:28 PM, John Hearns wrote:
Andreas,
This is a stupid reply, but please bear with me.
Not exactly GPFS related, but I once managed an
Andreas,
This is a stupid reply, but please bear with me.
Not exactly GPFS related, but I once managed an SGI CXFS (Clustered XFS
filesystem) setup.
We also had a new application which did post-processing One of the users
reported that a post-processing job would take about 30 minutes.
However wh
Dear group,
first a quick introduction: at KIT we are running a 20+PB storage system with
several large (1-9PB) file systems. We have a 14 node NSD server cluster and 5
small (~10 nodes) protocol node clusters which each mount one of the file
systems. The protocol nodes run server softw
The statement was always to be release
n-1 compatible. with release being (VRMF) 4.2.3.0
so all 4.2 release levels ought to be
compatible with all 4.1 levels. As Felipe pointed out below, the mmchconfig
RELEASE=latest will not touch the filesystem level. And if you are running remote clusters,
you
