Hello,
maybe someone on the list can confirm my current observation...or just saves a
bit of debugging time ;)
We are running GPFS 4.1.0.8 with CentOS 7.2.
With the recent update to systemd, GPFS is no longer started after a machine
reboot.
I traced this back to systemd and the /etc/init.d/gpfs
Hello,
we will soon start to deploy CES in our clusters, however two questions popped
up.
- According to the "CES NFS Support" in the "Implementing Cluster Export
Services" documentation, DNS round-robin might lead to corrupted data with
NFSv3:
If a DNS Round Robin (RR) entry name is used t
Yep, have look at this Gist [1]
The unit files assumes some paths and users, which are created during the
installation of my RPM.
[1] https://gist.github.com/stdietrich/b3b985f872ea648d6c03bb6249c44e72
Regards,
Stefan
- Original Message -
> From: "Greg Lehmann"
> To: gpfsug-discuss@spe
Hello,
I am currently trying to understand an issue with ACLs and how GPFS handles the
umask.
The filesystem is configured for NFS4 ACLs only (-k nfs4), filesets have been
configured for chmodAndUpdateACL and the access is through a native GPFS client
(v4.2.3).
If I create a new file in a dire
Hello,
during reading the upgrade docs for ESS 5.2.0, I noticed a change in the IPoIB
mode.
Now it specifies, that datagram (CONNECTED_MODE=no) instead of connected mode
should be used.
All earlier versions used connected mode.
I am wondering about the reason for this change?
Or is this only re
Hello Bryan,
at least changing multiple entries at once is possible.
You can copy /var/mmfs/ces/nfs-config/gpfs.ganesha.exports.conf to e.g. /tmp,
modify the export (remove/add nodes or options) and load the changed config via
"mmnfs export load "
That way, only a single restart is issued for G
Hi,
I am currently fiddling around with some nested NFSv4 exports and the differing
behaviour to NFSv3.
The environment is a GPFS 5.0.1 with enabled CES, so Ganesha is used as the NFS
server.
Given the following (pseudo) directory structure:
/gpfs/filesystem1/directory1
/gpfs/filesystem1/direc
mnfs export add" usage would show if it supports Pseudo option). Of course,
> you can manually do it (using CCR) as Ganesha itself allows it.
> Yes, NFSv3 has no pseudo traversal, it should work.
> Regards, Malahal.
>
>
> - Original message -
> From: "Dietric
Hi,
I am currently playing around with LDAP netgroups for NFS exports via CES.
However, I could not figure out how long Ganesha is caching the netgroup
entries?
There is definitely some caching, as adding a host to the netgroup does not
immediately grant access to the share.
A "getent netgroup
t may take about 30
> minutes to revoke the access.
> Added, "ganesha_mgr purge netgroup" to purge the cache to make the cache
> consistent with the actual configuration. It needs to be run on each node.
> Regards, Malahal.
>
>
> - Original message -
> From:
Hello Heiner,
the 64 vdisk limit per RG is still present in the latest ESS docs:
https://www.ibm.com/support/knowledgecenter/SSYSP8_5.3.5/com.ibm.spectrum.scale.raid.v5r04.adm.doc/bl1adv_vdisks.htm
For the other questions, no idea.
Regards,
Stefan
- Original Message -
> From: "Billich H
11 matches
Mail list logo