_The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._
1.83
2.9.4_
4.4.0-98-generic
Ubuntu 16.04.2 LTS n l
sudo s3fs bucket:/folder -o use_cache=/tmp -o allow_other -o uid=1001 -o mp_umask=002 -o multireq_max=20 -o endpoint=us-west-2 /s3 -f -d -d
Mar 20 06:22:43 s3fs[17907]: check services.
Mar 20 06:22:43 s3fs[17907]: check a bucket.
Mar 20 06:22:43 s3fs[17907]: URL is https://s3.amazonaws.com/bucket/folder/
Mar 20 06:22:43 s3fs[17907]: URL changed is https://bucket.s3.amazonaws.com/folder/
Mar 20 06:22:43 s3fs[17907]: computing signature [GET] [/folder/] [] []
Mar 20 06:22:43 s3fs[17907]: url is https://s3.amazonaws.com
Mar 20 06:22:43 s3fs[17907]: HTTP response code 400 was returned, returning EIO.
Mar 20 06:22:43 s3fs[17907]: curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: #012AuthorizationHeaderMalformed
Mar 20 06:22:43 s3fs[17907]: s3fs.cpp:s3fs_check_service(3768): Could not connect wrong region us-east-1, so retry to connect region us-west-2.
Mar 20 06:22:43 s3fs[17907]: check a bucket.
Mar 20 06:22:43 s3fs[17907]: URL is https://s3-us-west-2.amazonaws.com/bucket/folder/
Mar 20 06:22:43 s3fs[17907]: URL changed is https://bucket.s3-us-west-2.amazonaws.com/folder/
Mar 20 06:22:43 s3fs[17907]: computing signature [GET] [/folder/] [] []
Mar 20 06:22:43 s3fs[17907]: url is https://s3-us-west-2.amazonaws.com
Mar 20 06:22:43 s3fs[17907]: HTTP response code 404 was returned, returning ENOENT
Mar 20 06:22:43 s3fs[17907]: curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: #012NoSuchKey
Mar 20 06:22:43 s3fs[17907]: s3fs.cpp:s3fs_check_service(3806): bucket not found(host=https://s3-us-west-2.amazonaws.com) - result of checking service.
Mar 20 06:22:43 s3fs[17907]: s3fs.cpp:s3fs_exit_fuseloop(3361): Exiting FUSE event loop due to errors
Mar 20 06:22:43 s3fs[17907]: destroy
On the same machine, I used to be able to mount bucket:/folder with the command given above, however, after the machine is rebooted, it doesnt seem to be able to do so anymore. Help!
I am also facing the same issue.
I can mount the bucket as it is, but when I specify the sub-folder, it tells key do not exist
@mayying I solved it with aws console. Go to console, click on create folder and give name of the folder which is throwing error and try again it worked for me.
It do not make sense logically. But seems like a s3 bug.
Thanks @akhilputhiry, this was driving me crazy!
@akhilputhiry Akhil, i also stuck at the same issue. I followed above instructions and its not working for me. any suggestions to make it work.
Helped me
s3 = ::Aws::S3::Client.new(config)
s3.put_object(bucket: bucket, key: "path/to/directory/", content_type: 'application/x-directory')
Must specify Content-Type equal to application/x-directory
You guys should look at this: https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-could-not-mount-with-specifying-the-path-under-bucket
Does these symptoms occur in recent versions of s3fs, e.g., 1.85? I believe it improves permission and directory handling.
Closing due to inactivity. Please reopen if symptoms persist.
You guys should look at this: https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-could-not-mount-with-specifying-the-path-under-bucket
It is not workable with minio .
Most helpful comment
@mayying I solved it with aws console. Go to console, click on create folder and give name of the folder which is throwing error and try again it worked for me.
It do not make sense logically. But seems like a s3 bug.