Good point, Simon. Yes, it is a "file system quiesce" not a "fileset
quiesce" so it is certainly possible that mmfsd is unable to quiesce
because there are processes keeping files open in another fileset.
Nate Falk
IBM Spectrum Scale Level 2 Support
Software Defined Infrastructure, IBM
Hello Simon,
Sadly, that "1036" is not a node ID, but just a counter.
These are tricky to troubleshoot. Usually, by the time you realize it's
happening and try to collect some data, things have already timed out.
Since this mmdelsnapshot isn't something that's on a schedule from cron or
the
Hello Walter,
If you anticipate that the number of clients accessing this file system
may grow as high as 5000, then that is probably the value you should use
when creating the file system. The data structures (regions for example)
are allocated at file system creation time (more precisely at
I think I gave an internal link. Try this instead:
http://www.ibm.com/support/docview.wss?uid=ibm10716323
Nate Falk
IBM Spectrum Scale Level 2 Support
Software Defined Infrastructure, IBM Systems
E-mail: nf...@us.ibm.com
Find me on:
From: "Nathan Falk"
To: g
Hello Kevin,
No, you're not missing something. GPFS doesn't provide a means of
recursively modifying ACLs. It's not even all that easy to just modify one
ACL for one file (it's either mmeditacl, or mmgetacl > /tmp/acl.txt; vi
/tmp/acl.txt; mmputacl -i /tmp/acl.txt).
I've had a few queries
