mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #322] S3FS sometimes claims files are corrupted (images) when opening them directly #166
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#166
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 @AlmirKadric on GitHub (Jan 1, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/322
On OSX I can preview a file (press space), download (copy & paste) a file locally. However when I try to open it directly from the drive (e.g. double click on an image file and thus opening in
Previewapplication) if the filename has spaces it fails with the following error“File Name With Space.png” is damaged and can’t be opened. You should eject the disk.@AlmirKadric commented on GitHub (Jan 2, 2016):
after further investigation, it doesn't seem that the spaces in the file name are the issue. I found files with spaces which work and file without not working. Also seems to be isolated so far to images. Also copy & pasting them locally seems to solve the problem. Not sure why s3fs is claiming they are corrupted.
@ollietreend commented on GitHub (Feb 8, 2016):
@AlmirKadric Have you tried opening the image files in an application other than Preview? For example, what happens if you open it directly in Photoshop, or another image editor? I wonder whether Preview is doing something weird with the file which is causing that error message.
@ggtakec commented on GitHub (Mar 30, 2019):
We kept this issue open for a long time.
We launch new version 1.86, which fixed some problem(bugs).
Please use the latest version.
I will close this, but if the problem persists, please reopen or post a new issue.