[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gluster-devel] add-brick crashes client
From: |
Emmanuel Dreyfus |
Subject: |
[Gluster-devel] add-brick crashes client |
Date: |
Fri, 3 Aug 2012 04:52:11 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hi
I feel unlucky with release-3.3. Adding a pair of brick in a replicated
volume crashes a client that is using the volume.
Client log is attached. Here is glusterfsd bbacktrace in gdb:
Program terminated with signal 11, Segmentation fault.
#0 0xbbbc239c in synctask_wrap (old_task=0xbb711000) at syncop.c:120
120 task->ret = task->syncfn (task->opaque);
(gdb) bt
#0 0xbbbc239c in synctask_wrap (old_task=0xbb711000) at syncop.c:120
#1 0xbb8ccbe0 in swapcontext () from /lib/libc.so.12
Backtrace stopped: Not enough registers or memory available to unwind further
(gdb) print task
$1 = (struct synctask *) 0x0
This means pthread_getspecific(synctask_key) in synctask_get() returned
NULL, something I cannot explain. I see the logs complain about a volume
being down. This may be the cause of the problem since I have been able
to do a live brick-add later, once I restarterd glusterd/glusterfsd on
all bricks.
--
Emmanuel Dreyfus
address@hidden
log2
Description: Text document
- [Gluster-devel] add-brick crashes client,
Emmanuel Dreyfus <=
- Re: [Gluster-devel] add-brick crashes client, Emmanuel Dreyfus, 2012/08/03
- Re: [Gluster-devel] add-brick crashes client, Emmanuel Dreyfus, 2012/08/03
- Re: [Gluster-devel] add-brick crashes client, Amar Tumballi, 2012/08/03
- Re: [Gluster-devel] add-brick crashes client, Emmanuel Dreyfus, 2012/08/03
- Re: [Gluster-devel] add-brick crashes client, Emmanuel Dreyfus, 2012/08/03
- Re: [Gluster-devel] add-brick crashes client, Emmanuel Dreyfus, 2012/08/03
- Re: [Gluster-devel] add-brick crashes client, Emmanuel Dreyfus, 2012/08/03