Top posting because there are multiple questions
1. Atin, it is expected to fail if you don't have RDMA device or if it is
not configured.
2. Rafi and Dennis,
I was not able to determine from logs if it really is a RDMA bug. The brick
logs suggest that brick started and even accepted
Are there any workarounds to this? RDMA is configured on my servers.
Dennis
On Thu, Sep 29, 2016 at 7:19 AM, Atin Mukherjee wrote:
> Dennis,
>
> Thanks for sharing the logs.
>
> It seems like a volume configured created with tcp,rdma transport fails to
> start (atleast in
It seems like an actual bug, if youcan file a bug in bugzilla, that
would be great.
At least I don't see workaround for this issue, may be till the next
update is available with fix, you can use either rdma alone or tcp alone
volume.
Let me know whether this is acceptable, if so I can give you
Dennis,
Thanks for sharing the logs.
It seems like a volume configured created with tcp,rdma transport fails to
start (atleast in my local set up). The issue here is although the brick
process comes up, but glusterd receives a non zero ret code from the runner
interface which spawns the brick
On 09/30/2016 02:35 AM, Dennis Michael wrote:
>
> Are there any workarounds to this? RDMA is configured on my servers.
By this, I assume your rdma setup/configuration over IPoIB is working fine.
Can you tell us what machine you are using and whether SELinux is
configured on the machine or
Dennis,
It seems like that add-brick has definitely failed and the entry is not
committed into glusterd store. volume status and volume info commands are
referring the in-memory data for fs4 (which exist) but post a restart they
are no longer available. Could you run glusterd with debug log
On 09/27/2016 09:06 PM, Dennis Michael wrote:
Yes, the brick log /var/log/glusterfs/bricks/data-brick.log is created
on fs4, and the snippets showing the errors were from that log.
Unless I'm missing something, the snippet below is from glusterd's log
and not the brick's as is evident from
Yes, the brick log /var/log/glusterfs/bricks/data-brick.log is created on
fs4, and the snippets showing the errors were from that log.
Dennis
On Mon, Sep 26, 2016 at 5:58 PM, Ravishankar N
wrote:
> On 09/27/2016 05:25 AM, Dennis Michael wrote:
>
>> [2016-09-26
On 09/27/2016 05:25 AM, Dennis Michael wrote:
[2016-09-26 22:44:39.254921] E [MSGID: 106005]
[glusterd-utils.c:4771:glusterd_brick_start] 0-management: Unable to
start brick fs4:/data/brick
[2016-09-26 22:44:39.254949] E [MSGID: 106074]
[glusterd-brick-ops.c:2372:glusterd_op_add_brick]