[GH-ISSUE #209] ENOSPC returned some times #116

New issue

Closed

opened 2026-03-04 01:42:15 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:42:15 +03:00

Owner

Originally created by @UnitedMarsupials-zz on GitHub (Jul 16, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/209

We use s3fs as the backing store for an FTP-server. Files uploaded to us by FTP-only third-parties are then available for download via S3 bucket directly...

Today I got an report quoting our server erroring out with ENOSPC, which I find rather bizarre:

---> STOR ./foo-0.gz
<--- 150 Opening BINARY mode data connection for ./foo-0.gz
---- Accepted data connection from (ip.add.re.ss) port 41635
---- Closing data socket
<--- 451 No space left on device
---> SIZE ./foo-0.gz
<--- 213 29265920

The size of the s3 filesystem is, obviously humongous, so where could the limit be coming from? Could it be the amount of free space on the cache filesystem, that's the problem? Can s3fs be told to write directly to s3 -- either always, or when cache has not space? We do clean the cache up periodically, but, even if the cache fills up in between clean-ups, s3fs ought to degrade gracefully...

Originally created by @UnitedMarsupials-zz on GitHub (Jul 16, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/209 We use s3fs as the backing store for an FTP-server. Files uploaded to us by FTP-only third-parties are then available for download via S3 bucket directly... Today I got an report quoting our server erroring out with ENOSPC, which I find rather bizarre: ``` ---> STOR ./foo-0.gz <--- 150 Opening BINARY mode data connection for ./foo-0.gz ---- Accepted data connection from (ip.add.re.ss) port 41635 ---- Closing data socket <--- 451 No space left on device ---> SIZE ./foo-0.gz <--- 213 29265920 ``` The size of the s3 filesystem is, obviously humongous, so where could the limit be coming from? Could it be the amount of free space on the _cache_ filesystem, that's the problem? Can s3fs be told to write directly to s3 -- either always, or when cache has not space? We do clean the cache up periodically, but, even if the cache fills up in between clean-ups, s3fs ought to degrade gracefully...

kerem closed this issue

2026-03-04 01:42:16 +03:00

kerem commented

2026-03-04 01:42:16 +03:00

Author

Owner

@gaul commented on GitHub (Jul 16, 2015):

Which FTP server do you use? Can you strace it to determine which system calls it executes?

@gaul commented on GitHub (Jul 16, 2015): Which FTP server do you use? Can you `strace` it to determine which system calls it executes?

kerem commented

2026-03-04 01:42:17 +03:00

Author

Owner

@UnitedMarsupials-zz commented on GitHub (Jul 16, 2015):

We use mod_ftp inside Apache. The problem is not easy to reproduce -- haven't had it in 6 weeks since deploying this server to production, and it is gone now... Also, strace-ing Apache is notoriously difficult.

But my suspicion -- that saving the full file in cache is required , when cache is enabled at all -- is easy to confirm or deny, is not it? Thank you!

@UnitedMarsupials-zz commented on GitHub (Jul 16, 2015): We use mod_ftp inside Apache. The problem is not easy to reproduce -- haven't had it in 6 weeks since deploying this server to production, and it is gone now... Also, strace-ing Apache is notoriously difficult. But my suspicion -- that saving the full file in cache is _required_ , when cache is enabled at all -- is easy to confirm or deny, is not it? Thank you!

kerem commented

2026-03-04 01:42:17 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 17, 2016):

I'm sorry for that this issue had been left at a long period of time.

s3fs latest codes supports "ensure_diskfree" option, it keeps free disk space.
s3fs can not cache of cleaning, but this option will not be able to generate an ENOSPC by the s3fs cache.
Please try to use latest codes and this option.

Thanks in advance for your assistance.

@ggtakec commented on GitHub (Jan 17, 2016): I'm sorry for that this issue had been left at a long period of time. s3fs latest codes supports "ensure_diskfree" option, it keeps free disk space. s3fs can not cache of cleaning, but this option will not be able to generate an ENOSPC by the s3fs cache. Please try to use latest codes and this option. Thanks in advance for your assistance.

kerem commented

2026-03-04 01:42:17 +03:00

Author

Owner

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

We kept this issue open for a long time.
I will close this, but if the problem persists, please reopen or post a new issue.

@ggtakec commented on GitHub (Mar 29, 2019): We kept this issue open for a long time. I will close this, but if the problem persists, please reopen or post a new issue.

kerem referenced this issue

2026-03-04 01:53:30 +03:00

[PR #116] [MERGED] Supported signature version 4 #1350