Re: [MooseFS-Users] Memory leak with FUSE on mfs 1.6.26-1 ???

[Piotr R. K. <pio...@mo...>]

Hello,

MooseFS 1.6 is an outdated and not supported anymore version.
Is has a lot of bugs fixed in next releases: 2.0 and 3.0.
Also, versions 2.0 and 3.0 have a lot of improvements in algorithms, which makes MooseFS more stable and efficient.

We very recommend upgrading to MooseFS 2.0 which is a stable release.

You can find the complete upgrade guide here: https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf <https://moosefs.com/Content/Downloads/moosefs-upgrade.pdf>
Please also check all documentation: https://moosefs.com/documentation/moosefs-2-0.html <https://moosefs.com/documentation/moosefs-2-0.html>

Upgrade is a simple process - you mainly stop service, install a new version of package, check old configs and make appropriate changes in new config files and start the service.

(we have official repo now: https://moosefs.com/download/centosfedorarhel.html <https://moosefs.com/download/centosfedorarhel.html>)

Your data stay untouched.

In any case after stopping MFS Master, please copy /var/lib/metadata.mfs (on master) to safe place.

If you have any questions, please don’t hesitate to ask.


Best regards,

-- 
Piotr Robert Konopelko
MooseFS Technical Support Engineer | moosefs.com <https://moosefs.com/>
> On 25 Jun 2015, at 6:28 pm, pu...@go... <pu...@gm...> wrote:
> 
> Hi,
> I've got a pair of servers running mfs-1.6.26-1.el6.rf.x86_64
> for 10 months now, one is head/chunkserver/mfs-client, the other is chunkserver/head standby/metalogger.
> Worked fine until the CentOS update:
> just a few weeks ago the servers were upgraded
> from CentOS 6.4 to 6.6, and since then there is a problem with the
> memory consumption of the mfsmount/FUSE.
> Strange facts: kernel was NOT updated (due to a problem with DRBD-module)
> the FUSE-libs were also not updated, mfs-package is also the same as before.
> But only within 24 hours, sometimes 5 days, the memory for the mfsmount goes
> up to the max of the server's RAM, then is killed by the kernel (OOM).
> 
> Watching the PID of mfsmount with pmap showed that it allocates more memory over
> time, as the number of allocated memory-chunks is increasing: 
> watch "pmap $(pidof mfsmount)|grep anon|wc -l"
> In just 4 hours, this number goes up from 100 to 400, while allocating 4G memory.
> 
> Any ideas?
> 
> Kernel:
> 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014
> 
> FUSE:
> fuse-libs-2.8.3-4.el6.x86_64
> fuse-2.8.3-4.el6.x86_64
> 
> mount:
> mfsmount                /home                   fuse    mfsmaster=mfsmaster,_netdev,noatime,nodev,nosuid,noexec 0 0
> 
> 
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors 
> network devices and physical & virtual servers, alerts via email & sms 
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users