derrickchoi / s3fs

Automatically exported from code.google.com/p/s3fs
GNU General Public License v2.0
0 stars 0 forks source link

S3FS 1.40 using 3.6GB of memory! #184

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Detailed description of observed behavior:

After mlocate ran on our mounted s3fs bucket with between 500,000 and 1 million 
files (silly me, hadn't disabled it), s3fs process is suddenly consuming 3.6GB 
of memory, and has shown no signs of giving any of it back. I tried unmounting 
and remounting - no joy.

What steps will reproduce the problem - please be very specific and
detailed. (if the developers cannot reproduce the issue, then it is
unlikely a fix will be found)?

Allow mlocate to index a mounted bucket that contains many files.

===================================================================
The following information is very important in order to help us to help
you.  Omission of the following details may delay your support request or
receive no attention at all.
===================================================================
Version of s3fs being used (s3fs --version):

1.40

Version of fuse being used (pkg-config --modversion fuse):

2.8.4

System information (uname -a):

Linux ip-10-90-138-131 2.6.38-8-virtual #42-Ubuntu SMP Mon Apr 11 04:06:34 UTC 
2011 x86_64 x86_64 x86_64 GNU/Linux

Distro (cat /etc/issue):

Ubuntu 11.04 \n \l

s3fs command line used (if applicable):

s3fs s3.chickensmoothie.com /s3 -ouse_cache=/caches/s3 -oallow_other

/etc/fstab entry (if applicable):

s3fs syslog messages (grep s3fs /var/log/syslog):

Attached syslog shows all log messages from the beginning of the mlocate to the 
end

Original issue reported on code.google.com by N.sherl...@gmail.com on 11 May 2011 at 12:39

Attachments:

GoogleCodeExporter commented 8 years ago
s3fs has actually given back the memory now - after having held on to it for 6 
hours. I guess the umount/mount cleared it?

Original comment by N.sherl...@gmail.com on 11 May 2011 at 12:41

GoogleCodeExporter commented 8 years ago
unmount/mount should definitely clear any memory. Let us know if you're still 
seeing this is 1.61

Original comment by ben.lema...@gmail.com on 30 Aug 2011 at 4:00

GoogleCodeExporter commented 8 years ago
Hi,
I have the same problem )-:..
In my case s3fs allocates 7GB RAM of memory after a while.
Unmount/mount clears the memory for a while and than it happens again.
I've upgraded to 1.61 and it still happans.
I'm using fuse 2.8.4 on a CentOS 5.5 server..

Any help would be appreciated!

Thanks

Original comment by r...@codeoasis.com on 27 Nov 2011 at 9:58

GoogleCodeExporter commented 8 years ago
i face  the same problem...after few days memory keeps growing...is unmounting 
in cronjob and remounting is only option??

Original comment by srinivas...@gmail.com on 1 Mar 2012 at 1:42

GoogleCodeExporter commented 8 years ago
I am facing the same problem now, bnut it is consuming 11.1G. Is there another 
known fix instead umount/mount? 

Thanks in advance!

Original comment by ad...@onair.tv on 8 Jun 2012 at 5:33