mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-24 21:06:02 +03:00
[GH-ISSUE #2489] Can one increase the reported available space on mount? #1217
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1217
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
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!
@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:
You may be able to work around this by passing a larger value to
-o bucket_sizebut we should really figure out what the correct default should be. Maybe macOS reports a strange size for one of thestatvfsvalues, e.g.,stbuf->f_bsize= 1?@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=64PBAs 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.
@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?
@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 :)