[GH-ISSUE #2489] Can one increase the reported available space on mount? #1217

Closed
opened 2026-03-04 01:52:17 +03:00 by kerem · 4 comments
Owner

Originally created by @datumbox on GitHub (Jul 5, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2489

Additional Information

Version of s3fs being used (s3fs --version)

V1.93 (commit:unknown)

Details about issue

S3fs is a very handy solution for taking S3 backups using Ubuntu's Deja-dup. As of recently, they've introduced a check to ensure there is sufficient free available space on disk before taking a backup. Given that S3fs mounts the bucket and reports a 4GB free-space, that leads to errors. Example:

df -h --total /my/mount/point
Filesystem Size Used Avail Use% Mounted on
s3fs 4.0G 0 4.0G 0% /my/mount/point
total 4.0G 0 4.0G 0% -

I wonder if there is currently a way to increase this reported size to avoid issues with some downstream applications such as Deja-dup.

Thanks!

Originally created by @datumbox on GitHub (Jul 5, 2024). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2489 ### Additional Information #### Version of s3fs being used (`s3fs --version`) V1.93 (commit:unknown) ### Details about issue S3fs is a very handy solution for taking S3 backups using Ubuntu's Deja-dup. As of recently, [they've introduced](https://discourse.gnome.org/t/deja-dup-no-longer-works-with-s3fs/22008) a check to ensure there is sufficient free available space on disk before taking a backup. Given that S3fs mounts the bucket and reports a 4GB free-space, that leads to errors. Example: ``` df -h --total /my/mount/point Filesystem Size Used Avail Use% Mounted on s3fs 4.0G 0 4.0G 0% /my/mount/point total 4.0G 0 4.0G 0% - ``` I wonder if there is currently a way to increase this reported size to avoid issues with some downstream applications such as Deja-dup. Thanks!
kerem closed this issue 2026-03-04 01:52:17 +03:00
Author
Owner

@gaul commented on GitHub (Jul 5, 2024):

Which operating system do you run on? My Linux system reports 64 PB by default. The macOS logic differs though:

    stbuf->f_blocks = bucket_block_count;
    stbuf->f_frsize = stbuf->f_bsize;
    stbuf->f_bfree  = stbuf->f_blocks;
    stbuf->f_files  = UINT32_MAX;
    stbuf->f_ffree  = UINT32_MAX;
    stbuf->f_favail = UINT32_MAX;

You may be able to work around this by passing a larger value to -o bucket_size but we should really figure out what the correct default should be. Maybe macOS reports a strange size for one of the statvfs values, e.g., stbuf->f_bsize = 1?

<!-- gh-comment-id:2210509453 --> @gaul commented on GitHub (Jul 5, 2024): Which operating system do you run on? My Linux system reports 64 PB by default. The macOS logic differs though: ``` stbuf->f_blocks = bucket_block_count; stbuf->f_frsize = stbuf->f_bsize; stbuf->f_bfree = stbuf->f_blocks; stbuf->f_files = UINT32_MAX; stbuf->f_ffree = UINT32_MAX; stbuf->f_favail = UINT32_MAX; ``` You may be able to work around this by passing a larger value to `-o bucket_size` but we should really figure out what the correct default should be. Maybe macOS reports a strange size for one of the `statvfs` values, e.g., `stbuf->f_bsize` = 1?
Author
Owner

@datumbox commented on GitHub (Jul 5, 2024):

Hi @gaul. Thanks so much for your ultra prompt reply.

I'm on Ubuntu 24.04 and I've faced the issue after updating from 22.04.

I've updated my mounting command as you proposed:
s3fs bucket_name_goes_here /my/mount/point -o bucket_size=64PB

As you indicated, this indeed updates the reported free size. I've tested the integration with Deja-dup and everything works as expected.

Thank you very much for your help on this. Apologies for raising it as an issue on the main repo, but I hope others will find it useful.

<!-- gh-comment-id:2210588838 --> @datumbox commented on GitHub (Jul 5, 2024): Hi @gaul. Thanks so much for your ultra prompt reply. I'm on Ubuntu 24.04 and I've faced the issue after updating from 22.04. I've updated my mounting command as you proposed: `s3fs bucket_name_goes_here /my/mount/point -o bucket_size=64PB` As you indicated, this indeed updates the reported free size. I've tested the integration with Deja-dup and everything works as expected. Thank you very much for your help on this. Apologies for raising it as an issue on the main repo, but I hope others will find it useful.
Author
Owner

@gaul commented on GitHub (Jul 5, 2024):

But why is the default behavior wrong? I wonder if something differs between my Fedora system and your Ubuntu system?

<!-- gh-comment-id:2210591925 --> @gaul commented on GitHub (Jul 5, 2024): But why is the default behavior wrong? I wonder if something differs between my Fedora system and your Ubuntu system?
Author
Owner

@datumbox commented on GitHub (Jul 5, 2024):

@gaul I assume you mean that the default value shouldn't have lead to a 4GB free space? If you want me to make any specific checks on my system to provide more info, I'm down to doing it. Just let me know :)

<!-- gh-comment-id:2210936249 --> @datumbox commented on GitHub (Jul 5, 2024): @gaul I assume you mean that the default value shouldn't have lead to a 4GB free space? If you want me to make any specific checks on my system to provide more info, I'm down to doing it. Just let me know :)
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#1217
No description provided.