[GH-ISSUE #797] Memory leak with s3fs mount #458

Closed
opened 2026-03-04 01:45:44 +03:00 by kerem · 7 comments
Owner

Originally created by @raodrl on GitHub (Jul 9, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/797

Additional Information

Issue details under Details about issue section

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System V1.83(commit:3e4002d) with OpenSSL

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

2.9.2

System information (uname -r)

_command result: 3.10.0-693.11.6.el7.x86_64

Distro (cat /etc/issue)

command result: cat /etc/issue
\S
Kernel \r on an \m

s3fs command line used (if applicable)

s3fs -o allow_other /s3mntdirectory -o passwd_file=/etc/passwd-s3fs,gid=app_gid,umask=007

/etc/fstab entry (if applicable):

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Details about issue

I updated s3fs version from V1.82 with latest version as i have memory leaks on the mount. even after update i still see the memory leak on the mount point as i had seen its gradually increasing the usage though no one uses the mount and is idle. Please let me know if i had missed anything during update. Thanks.

Originally created by @raodrl on GitHub (Jul 9, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/797 ### Additional Information Issue details under Details about issue section #### Version of s3fs being used (s3fs --version) Amazon Simple Storage Service File System V1.83(commit:3e4002d) with OpenSSL #### Version of fuse being used (pkg-config --modversion fuse) 2.9.2 #### System information (uname -r) _command result: 3.10.0-693.11.6.el7.x86_64 #### Distro (cat /etc/issue) _command result: cat /etc/issue_ \S Kernel \r on an \m #### s3fs command line used (if applicable) s3fs -o allow_other <s3Bucket Name> /s3mntdirectory -o passwd_file=/etc/passwd-s3fs,gid=app_gid,umask=007 #### /etc/fstab entry (if applicable): ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` ``` ### Details about issue I updated s3fs version from V1.82 with latest version as i have memory leaks on the mount. even after update i still see the memory leak on the mount point as i had seen its gradually increasing the usage though no one uses the mount and is idle. Please let me know if i had missed anything during update. Thanks.
kerem closed this issue 2026-03-04 01:45:44 +03:00
Author
Owner

@gaul commented on GitHub (Jan 24, 2019):

Can you provide specific information on this possible leak, e.g., how many bytes per hour, does the amount level off after some time? Note that s3fs has an in-memory stat cache which will grow up to 100,00 entries or 40 MB.

<!-- gh-comment-id:457032816 --> @gaul commented on GitHub (Jan 24, 2019): Can you provide specific information on this possible leak, e.g., how many bytes per hour, does the amount level off after some time? Note that s3fs has an in-memory stat cache which will grow up to 100,00 entries or 40 MB.
Author
Owner

@raodrl commented on GitHub (Jan 24, 2019):

Thanks for the response. I don't know how many bytes per hour here. But the leak happens on the mount continuously and gradually increasing the memory usage and goes back to zero unless i unmount it. Say on a 8GB memory linux server per day its usage goes up by 1.5% though there is no activity on the mount .

<!-- gh-comment-id:457257115 --> @raodrl commented on GitHub (Jan 24, 2019): Thanks for the response. I don't know how many bytes per hour here. But the leak happens on the mount continuously and gradually increasing the memory usage and goes back to zero unless i unmount it. Say on a 8GB memory linux server per day its usage goes up by 1.5% though there is no activity on the mount .
Author
Owner

@gaul commented on GitHub (Jan 24, 2019):

Perhaps updatedb crawls your mount? See:

https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-why-does-my-cpu-spike-at-certain-times-of-the-day

Without additional information it is difficult to tell if there is a leak or not.

<!-- gh-comment-id:457307792 --> @gaul commented on GitHub (Jan 24, 2019): Perhaps `updatedb` crawls your mount? See: https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-why-does-my-cpu-spike-at-certain-times-of-the-day Without additional information it is difficult to tell if there is a leak or not.
Author
Owner

@ggtakec commented on GitHub (Mar 29, 2019):

We launched new version(1.86) which is fixed bugs about some memory leak.
If you can, please use latest version or master branch code.
Thanks in advance for your assistance.

<!-- gh-comment-id:477894395 --> @ggtakec commented on GitHub (Mar 29, 2019): We launched new version(1.86) which is fixed bugs about some memory leak. If you can, please use latest version or master branch code. Thanks in advance for your assistance.
Author
Owner

@zhou-hongyu commented on GitHub (May 1, 2019):

We launched new version(1.86) which is fixed bugs about some memory leak.
If you can, please use latest version or master branch code.
Thanks in advance for your assistance.

Hey @ggtakec , how am I able to download the version(1.86)? I don't see it there

<!-- gh-comment-id:488294830 --> @zhou-hongyu commented on GitHub (May 1, 2019): > We launched new version(1.86) which is fixed bugs about some memory leak. > If you can, please use latest version or master branch code. > Thanks in advance for your assistance. Hey @ggtakec , how am I able to download the version(1.86)? I don't see it there
Author
Owner

@gaul commented on GitHub (May 2, 2019):

1.85 is the latest version; 1.86 is a typo.

<!-- gh-comment-id:488506964 --> @gaul commented on GitHub (May 2, 2019): 1.85 is the latest version; 1.86 is a typo.
Author
Owner

@gaul commented on GitHub (Feb 3, 2020):

Closing due to inactivity. Please reopen if symptoms persist.

<!-- gh-comment-id:581293419 --> @gaul commented on GitHub (Feb 3, 2020): Closing due to inactivity. Please reopen if symptoms persist.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#458
No description provided.