mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #1982] Write fails, not enough free space - Macos #1003
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#1003
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 @WGandy on GitHub (Jul 11, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1982
Perhaps I'm missing something simple here but here goes.
Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.91
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
$ pkg-config --modversion fuse
2.9.7
GNU/Linux Distribution, if applicable (cat /etc/os-release)
Macos Big Sur 11.6.7
Details about issue
In finder the status bar shows 1MB of free space when I'm browsing the S3 bucket. If I try to copy a file (50MB or so) into the folder it spends some time preparing and then I get this error
The item “myfilename” can’t be copied because there isn’t enough free space.It seems that there needs to be some kind of cache for writes on the Mac machine? The bucket has plenty of space for this.
@suminb commented on GitHub (Aug 29, 2022):
I have a similar issue.
df -hcommand shows the following (note that the volume size is 1MB):Is there any way to manually adjust the volume size?
@ggtakec commented on GitHub (Sep 24, 2022):
@WGandy @suminb I'm sorry for late reply.
I uploaded the fix in #2037.
I think the corrections for sizes you can see by df command are fixed in this PR.
If you can, please build the code in that PR and give it a try.
The PR code will be reviewed and then merged into master.
@ggtakec commented on GitHub (Sep 25, 2022):
PR #2037 was merged.
If you can try it with master's code, please try it.
We will close this issue, but if the problem still exists, please reopen it.