[GH-ISSUE #814] Cannot read files through S3 mount #471

Closed
opened 2026-03-04 01:45:53 +03:00 by kerem · 2 comments
Owner

Originally created by @hhg7 on GitHub (Aug 30, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/814

Hello,

I am attempting to read files on AWS, simply read them with a perl script. However, the mount I have on my Ubuntu system will hang when I try to even look at the contents of the file, e.g. head file.txt will never complete.

How can I read the files on the S3 mount?

I'm using s3fs 1.61 on Linux kernel 4.15.0-33-generic on Ubuntu 18.04.1 LTS with fuse version 2.9.7

Originally created by @hhg7 on GitHub (Aug 30, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/814 Hello, I am attempting to read files on AWS, simply read them with a perl script. However, the mount I have on my Ubuntu system will hang when I try to even look at the contents of the file, e.g. `head file.txt` will never complete. How can I read the files on the S3 mount? I'm using s3fs 1.61 on Linux kernel 4.15.0-33-generic on Ubuntu 18.04.1 LTS with fuse version 2.9.7
kerem closed this issue 2026-03-04 01:45:54 +03:00
Author
Owner

@gaul commented on GitHub (Jan 24, 2019):

Could you retest with a newer version of s3fs? 1.61 is almost 8 years old.

<!-- gh-comment-id:457031672 --> @gaul commented on GitHub (Jan 24, 2019): Could you retest with a newer version of s3fs? 1.61 is almost 8 years old.
Author
Owner

@gaul commented on GitHub (Mar 15, 2019):

Please reopen if you can demonstrate these symptoms on the latest release version, 1.85.

<!-- gh-comment-id:473196656 --> @gaul commented on GitHub (Mar 15, 2019): Please reopen if you can demonstrate these symptoms on the latest release version, 1.85.
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#471
No description provided.