Hi,
The NFS just crashed again, latest bt;
(gdb) bt#0 0x7f0b71a9f210 in pthread_spin_lock () from
/lib64/libpthread.so.0#1 0x7f0b72c6fcd5 in fd_anonymous (inode=0x0) at
fd.c:804#2 0x7f0b64ca5787 in shard_common_inode_write_do
(frame=0x7f0b707c062c, this=0x7f0b6002ac10) at shard.c:
On Mon, Aug 1, 2016 at 3:40 PM, Yannick Perret wrote:
> Le 29/07/2016 à 18:39, Pranith Kumar Karampuri a écrit :
>
>
>
> On Fri, Jul 29, 2016 at 2:26 PM, Yannick Perret <
> yannick.per...@liris.cnrs.fr> wrote:
>
>> Ok, last try:
>> after investigating more versions I found that FUSE client leaks
I was testing this with VMware workstation with 3 node v3.7.13 3Gram 2vcpu
each,
Volume Name: v1
Type: Replicate
Volume ID: 52451d84-4176-4ec1-96e8-7e60d02a37f5
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 192.168.3.71:/gfs/b1/v1
Brick2: 192.168.3.72:/gfs/b1/v1
Many thanks,
here's the results;
(gdb) p cur_block$15 = 4088(gdb) p last_block$16 = 4088(gdb) p
local->first_block$17 = 4087(gdb) p odirect$18 = _gf_false(gdb) p fd->flags$19
= 2(gdb) p local->call_count$20 = 2
If you need more core dumps, i have several files i can upload.
--
Respectfully
Sorry I didn't make myself clear. The reason I asked YOU to do it is
because i tried it on my system and im not getting the backtrace (it's all
question marks).
Attach the core to gdb.
At the gdb prompt, go to frame 2 by typing
(gdb) f 2
There, for each of the variables i asked you to get the va
Hello
There is a memleak (as reported by valgrind) in all gluster versions,
even in 3.8.1 (although leak is smaller)
gluster: 3.8.1
valgrind: 3.11.0
simple C code:
#include
#include
#include
#include
#include
#include
int main (int argc, char** argv) {
glfs_t *fs = NULL;
//
Hi,
How to get the results of the below variables ? i cant get the results from gdb.
--
Respectfully
Mahdi A. Mahdi
From: kdhan...@redhat.com
Date: Mon, 1 Aug 2016 15:51:38 +0530
Subject: Re: [Gluster-users] Gluster 3.7.13 NFS Crash
To: mahdi.ad...@outlook.com
CC: gluster-users@glust
Could you also print and share the values of the following variables from
the backtrace please:
i. cur_block
ii. last_block
iii. local->first_block
iv. odirect
v. fd->flags
vi. local->call_count
-Krutika
On Sat, Jul 30, 2016 at 5:04 PM, Mahdi Adnan
wrote:
> Hi,
>
> I really appreciate if someo
Le 29/07/2016 à 18:39, Pranith Kumar Karampuri a écrit :
On Fri, Jul 29, 2016 at 2:26 PM, Yannick Perret
mailto:yannick.per...@liris.cnrs.fr>>
wrote:
Ok, last try:
after investigating more versions I found that FUSE client leaks
memory on all of them.
I tested:
- 3.6.7 c
