-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot mount "Input/output error" #365
Comments
workdir and upperdir must be two different directories, but they must be on the same file system |
Thank you! That is one thing I was unsure about. When you say same file system, do you mean it can be a entirely different goofys s3 mount location (as long as its still a fuse s3 mount), or should be the same disk (meaning i would need to make two folders on a disk, one for data and one for workdir)? I had tried making workdir to something like workdir=/mnt/html/upload_wasabi/overlay but that doesn't work either. Also, in my particular use case where these same disks are mounted on many machines, I would want to make sure workdir contents are shared correct? |
I tried
But still same error. Full goofys log
|
could you run fuse-overlayfs with the EDIT: nevermind, sorry, I see you already did |
does it work if you try as root with native overlay? |
I tried native overlay but it said that this type of filesystem was not supported (in the case of goofys aws/wasabi s3) which is why I then moved onto migratefs. So i tried something like
I should mention I have been trying to use fuse-overlayfs inside a docker instance. (of amazonlinux2). I tested migratefs on a production server with same results but have not yet tried fuse-overlayfs. Could this be a cause? |
libfuse 3.2.6
fuse-overlayfs 1.8.2 prebuilt x86_64
amazonlinux2
I have been trying to use fuse-overlayfs to merge two goofys s3 folders.
I succeeded using migratefs (a fork of fuse-overlayfs) but had a different issue (copyup permission issue) so I am now trying fuse-overlayfs without copyup feature.
I call the following
Result
On the upper directories goofys debug, the error seems to be:
Full upper goofys debug log:
Any ideas would be appreciated"
Thank you
The text was updated successfully, but these errors were encountered: