mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #42] Fuse 2.8.4 really required? #26
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#26
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 @paulm17 on GitHub (Jun 27, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/42
Hi,
I'm using centos 6.5. It comes with Fuse 2.8.3.
Is there any particular reason why fuse 2.8.4 is required? Are there any problems with 2.8.3?
Thanks
@thenickdude commented on GitHub (Jun 28, 2014):
This is where it was decided that 2.8.4 should be the new minimum:
https://code.google.com/p/s3fs/issues/detail?id=136#c23
Sounds like there was a bug in older FUSE releases that caused S3FS to freeze.
@paulm17 commented on GitHub (Jun 28, 2014):
Thanks for taking the time to respond.
I actually did compile the latest s3fs into an rpm with fuse 2.8.3. But now I know it has this instability. I'll use my compiled versions of fuse 2.9.3 with centos 6 and s3fs against 2.9.3. I'll go with this until Centos 7 comes out offically.
Thanks
@juliogonzalez commented on GitHub (Sep 23, 2018):
I know this is an old issue, but for reference, since I am now packaging for Fedora and I need to reference this in relation to CentOS6:
Reading the original issue at Google Code doesn't make clear to me that the culprit was fuse, but anyway, right now the testsuite just doesn't pass anymore with fuse 2.8.3 for some basic functionality.