[Bugs] [Bug 1738878] FUSE client's memory leak

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 30 09:02:16 UTC 2019


--- Comment #10 from Sergey Pleshkov <s.pleshkov at hostco.ru> ---

Yesterday I upgraded the client to version 6.5 and set the lru-limit - the
problem with the continuous occupation of RAM was solved by this workaround.
Gathered a couple of state dumps if anybody want to see them.

But ran into another problem after this update
Server software version 5.5, client version 6.5 - every time I write a file to
a mounted shared folder, I see this error in the logs (with or without
lru-limit option)

[2019-08-30 08:31:04.763118] E [fuse-bridge.c:220:check_and_dump_fuse_W] (-->
/lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7f361d877a3b] (-->
/usr/lib64/glusterfs/6.5/xlator/mount/fuse.so(+0x81d1)[0x7f3614c261d1] (-->
/usr/lib64/glusterfs/6.5/xlator/mount/fuse.so(+0x8aaa)[0x7f3614c26aaa] (-->
/lib64/libpthread.so.0(+0x7dd5)[0x7f361c6b5dd5] (-->
/lib64/libc.so.6(clone+0x6d)[0x7f361bf7dead] ))))) 0-glusterfs-fuse: writing to
fuse device failed: No such file or directory

Files are created in shared folder, on other clients I see them, the contents
can be updated.

I need to open another bug on this issue?

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Bugs mailing list