[GH-ISSUE #347] Disk space error for other things #182

New issue

Closed

opened 2026-03-04 01:43:02 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:43:02 +03:00

Owner

Originally created by @will-parsons on GitHub (Feb 5, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/347

# s3fs -o noatime,use_cache=/tmp/s3fs_cache BUCKET-NAME /mnt/s3fs/
s3fs: There is no enough disk space for used as cache(or temporary) directory by s3fs.

I had plenty of disk space. In this case, /tmp/s3fs_cache didn't exist. When I created it, the mount worked fine:

# mkdir /tmp/s3fs_cache
# s3fs -o noatime,use_cache=/tmp/s3fs_cache BUCKET-NAME /mnt/s3fs/
# tail -1 /proc/mounts 
s3fs /mnt/s3fs fuse.s3fs rw,nosuid,nodev,noatime,user_id=0,group_id=0 0 0

Additionally, my first attempt gave a similar error because SElinux was enabled and, rightly so, s3fs wasn't allowed to write to /tmp/ for the cache. Disabled SElinux and the mount worked as above.

Suggestions:

Check use_cache directory exists when mounting, and either create it or throw a meaningful error
Check we can get a write lock on the use_cache directory before attempting to use it

Thanks :)

Originally created by @will-parsons on GitHub (Feb 5, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/347 ``` # s3fs -o noatime,use_cache=/tmp/s3fs_cache BUCKET-NAME /mnt/s3fs/ s3fs: There is no enough disk space for used as cache(or temporary) directory by s3fs. ``` I had plenty of disk space. In this case, `/tmp/s3fs_cache` didn't exist. When I created it, the mount worked fine: ``` # mkdir /tmp/s3fs_cache # s3fs -o noatime,use_cache=/tmp/s3fs_cache BUCKET-NAME /mnt/s3fs/ # tail -1 /proc/mounts s3fs /mnt/s3fs fuse.s3fs rw,nosuid,nodev,noatime,user_id=0,group_id=0 0 0 ``` Additionally, my first attempt gave a similar error because SElinux was enabled and, rightly so, s3fs wasn't allowed to write to /tmp/ for the cache. Disabled SElinux and the mount worked as above. Suggestions: - [x] Check `use_cache` directory exists when mounting, and either create it or throw a meaningful error - [ ] Check we can get a write lock on the `use_cache` directory before attempting to use it Thanks :)

kerem closed this issue

2026-03-04 01:43:03 +03:00

kerem commented

2026-03-04 01:43:03 +03:00

Author

Owner

@ggtakec commented on GitHub (Feb 6, 2016):

@will-parsons I merged new codes #351.
It throw a error at executing s3fs. so I think that s3fs should not make cache directory, it should be existed before executing s3fs.

@ggtakec commented on GitHub (Feb 6, 2016): @will-parsons I merged new codes #351. It throw a error at executing s3fs. so I think that s3fs should not make cache directory, it should be existed before executing s3fs.

kerem commented

2026-03-04 01:43:04 +03:00

Author

Owner

@ggtakec commented on GitHub (Apr 2, 2017):

@will-parsons
This problem was fixed by #351, but this fix causes a problem at OS startup like #538.
Therefore, check_cache_dir_exist option was added.
To check the cache directory when starting s3fs, specify this new option together.

It will be revised again, and will inconvenience you.
Regards,

@ggtakec commented on GitHub (Apr 2, 2017): @will-parsons This problem was fixed by #351, but this fix causes a problem at OS startup like #538. Therefore, check_cache_dir_exist option was added. To check the cache directory when starting s3fs, specify this new option together. It will be revised again, and will inconvenience you. Regards,

kerem referenced this issue

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

[PR #182] [CLOSED] text compleat encryption pull #1386