keiviw: Despite the fact that friendly greetings are nice, please ask your question. Carefully identify your problem in such a way that when a volunteer has a few minutes, they can offer you a potential solution. These are volunteers, so be patient. Answers may come in a few minutes, or may take hours. If you're still in the channel, someone will eventually offer an answer.

Hello, I was wondering if anyone knew of an easy way to get the volume id on a box that is mounting the volume. It is mounting the volume using the native client (ie: mount -t glusterfs <ip>:/<volumename> <locationToMountTo>

ndevos: I'll look into that .meta folder. im not seeing it on the mount currently though. (any suggestions on how to turn it on would be appreciated :) ) also I can only get the trusted.glusterfs.volume-id attribute off of the brick, but not on the mount

I have a replicated 3-node cluster and at one point, I am copying about 16 large files to the mount. During this time, we get the error message "[rpc-clnt-ping.c:165:rpc_clnt_ping_timer_expired] 0-appian-client-2: server 10.125.10.102:49152 has not responded in the last 42 seconds, disconnecting." and the client becomes read-only.

Sounds good, JoeJulian. My guess is that all the threads are taken due to the large file copying and therefore, when the client pings to check if the server is there, it doesn't get a response within 42 seconds, so therefore it decides to disconnect. The disconnect happens to two servers out of three, so therefore, the client doesn't have quorum and turns to read-only mode. Increasing the ping-timeout gives the c

Yeah, just double checked. Pings are part of the rpc library and are implmented by the client and server translators (the translators that actually interface with the network). They never get to the performance.io-thread translator.

Hi guys. I'm stuck healing some files, I have all the bricks mounted, I stat the file but on one of the bricks, the file it's only a 0-sized file. In the other two breaks I have it's ok. Any clue of what can be wrong here? I'm using 3.5.7, but updating is not an option.