My two cents,
Have the SELinux enabled on my RH7.3 cluster (where CES nodes are RH 7,3).
GPFS latest version(4.2.2) is on the cluster.
Non SELinux env, should mount w/o issues as well
Tried mounting for 50 iters as V3 for 2 different mounts from 4 client
nodes. Ran successfully. My client
On Wed, 04 Jan 2017 00:14:21 +0100, Jan-Frode Myklebust said:
> This looks like Spectrum Archive v1.2.1.0 (Build 10230). Newest version
> available on fixcentral is v1.2.2.0, but it doesn't support GPFS v4.2.2.x
> yet.
That's what I was afraid of. OK, shelve that option, and call IBM for the
On 1/3/17 4:40 PM, Laurence Horrocks-Barlow wrote:
> Andrew,
>
> You may have been stung by:
>
> 2.34 What considerations are there when running on SELinux?
>
> https://www.ibm.com/support/knowledgecenter/en/STXKQY/gpfsclustersfaq.html?view=kc#selinux
se is disabled here.
Also if you strace the
nsds and ces nodes are RHEL 7.3
nfsv3 clients are old ubuntu lucid.
we finally just removed the IP that seemed to... when moved to a ces
node caused it to stop responding.
it hung up a few more times but has been working fine now for the last
few hours.
maybe a bad client apple out there
This looks like Spectrum Archive v1.2.1.0 (Build 10230). Newest version
available on fixcentral is v1.2.2.0, but it doesn't support GPFS v4.2.2.x
yet.
-jf
On Tue, Jan 3, 2017 at 11:56 PM, Valdis Kletnieks
wrote:
> So we have GPFS Advanced 4.2.1 installed, and the
So we have GPFS Advanced 4.2.1 installed, and the following RPMs:
% rpm -qa 'ltfs*' | sort
ltfsle-2.1.6.0-9706.x86_64
ltfsle-library-2.1.6.0-9706.x86_64
ltfsle-library-plus-2.1.6.0-9706.x86_64
ltfs-license-2.1.0-20130412_2702.x86_64
ltfs-mig-1.2.1.1-10232.x86_64
What release of "Spectrum
Andrew,
You may have been stung by:
2.34 What considerations are there when running on SELinux?
https://www.ibm.com/support/knowledgecenter/en/STXKQY/gpfsclustersfaq.html?view=kc#selinux
I've see this issue on a customer site myself.
Matt,
Could you increase the logging verbosity and check
Matt
What Operating system are you running?
I have an open PMR at present with something very similar
when ever we publish an NFS export via the protocol nodes the nfs service stops, although we have no issues publishing SMB exports.
I"m waiting on some testing by the customer but L3 support
On Tue, 03 Jan 2017 14:27:17 -0600, Matt Weil said:
> this follows the IP what ever node the ip lands on. the ganesha.nfsd
> process seems to stop working. any ideas? there is nothing helpful in
> the logs.
Does it in fact "stop working", or are you just having a mount issue? Do
already
this follows the IP what ever node the ip lands on. the ganesha.nfsd
process seems to stop working. any ideas? there is nothing helpful in
the logs.
time mount ces200:/vol/aggr14/temp403 /mnt/test
mount.nfs: mount system call failed
real1m0.000s
user0m0.000s
sys 0m0.010s
10 matches
Mail list logo