kashian's questions

I have an ec2 instance with an ephemeral disk. This instance goes down every night and boots up when needed. I used cloud-init to format the ephemeral disk and this works correct but only once. when this machine is stopped and started (and the ephemeral disk disappears) it no longer runs this cloud-init module. I have attempted to override the default frequency by declaring the module in /etc/cloud/cloud.cfg as

cloud_init_modules:
 - [ disk-setup, always ]

And I have tried changing /usr/lib/python2.7/dist-packages/cloudinit/config/cc_disk_setup.py by changing the following variable

frequency = ALWAYS

Is it possible to force the module to run on every boot or do i need to approach this differently?

We are running GlusterFS replication server on 2 nodes and we have 2 clients. Self healing daemon is enabled. Each client is connected to a different server using the Gluster client. We have a lot of very small files on the Gluster volume.

We use GlusterFS 3.9.1 from the official GlusterFS APT Repositories on a Debian Jessie system.

The issue we are facing with is that one of the servers is at 0.1-0.5 load average while the other is at 200. The server with the high load also has a huge amount of data being streamed constantly to both the client nodes. This data stream continues even when the clients are not reading writing data.

The following values are measured by nload and iftop :

server: outgoing 35-40 MB/s

Two clients: incoming 17-20 MB/s

Our performance on the Gluster client is very poor. An ls can take up to 10 second to complete, and our app works extremely slow.

Servers and clients are connecting over an internal data-center network and can handle much more bandwidth so this is not a limiting factor.

My two main questions are :

1: Are these differences in server load normal behavior for GlusterFS and what causes this?

2: Why is there such a high constant data stream to clients form one of the servers.

I cannot seem to find any information concerning this in the Gluster Documentation or on the Internet.

this is a strange issue I've been struggling with some time now. I have a working ldap and authentication via pam on debian 8. I have successful tested pam_mkhomedir and I got a home directory for the logged in user with ownership username:groupname.

In the second phase of the project I created an nfs (nfsv4) mount on /home/nfs I want to put my home dirs there so I can share them across servers. The problem I face is when I use pam_mkhomdir to create the home dir it has ownership nobody:nogroup. If I create this manually logged in as an ldap user I get the correct ownership username:groupname so I am fairly sure nfs can deal with the ldap usernames.

idmap is configured to use nsswitch and

id ldapuser

returns the same info on both the nfs client and server. Also ldap login works on both of them

does anyone have an idea as to why pam_mkhomdir would default to nobody:nogroup while nfs works with ldap users?