starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #734] Unable to mount a specific folder #418

New issue

Closed

opened 2026-03-04 01:45:24 +03:00 by kerem · 9 comments

kerem commented

2026-03-04 01:45:24 +03:00

Owner

Originally created by @mayying on GitHub (Mar 20, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/734

Additional Information

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.

Version of s3fs being used (s3fs --version)

1.83

Version of fuse being used (pkg-config --modversion fuse)

2.9.4_

System information (uname -r)

4.4.0-98-generic

Distro (cat /etc/issue)

Ubuntu 16.04.2 LTS \n \l

s3fs command line used (if applicable)

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

/etc/fstab entry (if applicable):

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)

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: #012AuthorizationHeaderMalformedThe authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-west-2'us-west-2
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: #012NoSuchKeyThe specified key does not exist.folder/
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

detail about the issue

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!

Originally created by @mayying on GitHub (Mar 20, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/734 ### Additional Information _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._ #### Version of s3fs being used (s3fs --version) 1.83 #### Version of fuse being used (pkg-config --modversion fuse) 2.9.4_ #### System information (uname -r) 4.4.0-98-generic #### Distro (cat /etc/issue) Ubuntu 16.04.2 LTS \n \l #### s3fs command line used (if applicable) 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 #### /etc/fstab entry (if applicable): ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) 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: <?xml version="1.0" encoding="UTF-8"?>#012<Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-west-2'</Message><Region>us-west-2</Region><RequestId></RequestId><HostId></HostId></Error> 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: <?xml version="1.0" encoding="UTF-8"?>#012<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>folder/</Key><RequestId></RequestId><HostId></HostId></Error> 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 #### detail about the issue 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!

kerem closed this issue

2026-03-04 01:45:24 +03:00

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@akhilputhiry commented on GitHub (Apr 11, 2018):

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

@akhilputhiry commented on GitHub (Apr 11, 2018): 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

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@akhilputhiry commented on GitHub (Apr 11, 2018):

@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.

@akhilputhiry commented on GitHub (Apr 11, 2018): @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.

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@camilhord commented on GitHub (May 30, 2018):

Thanks @akhilputhiry, this was driving me crazy!

@camilhord commented on GitHub (May 30, 2018): Thanks @akhilputhiry, this was driving me crazy!

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@shivkaundal commented on GitHub (Aug 23, 2018):

@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.

@shivkaundal commented on GitHub (Aug 23, 2018): @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.

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@Stanislav-Lapata commented on GitHub (Feb 12, 2019):

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

@Stanislav-Lapata commented on GitHub (Feb 12, 2019): Helped me ```ruby 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

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@kuafou commented on GitHub (Oct 12, 2019):

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

@kuafou commented on GitHub (Oct 12, 2019): 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

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

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

Does these symptoms occur in recent versions of s3fs, e.g., 1.85? I believe it improves permission and directory handling.

@gaul commented on GitHub (Oct 24, 2019): Does these symptoms occur in recent versions of s3fs, e.g., 1.85? I believe it improves permission and directory handling.

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@gaul commented on GitHub (Feb 3, 2020):

Closing due to inactivity. Please reopen if symptoms persist.

@gaul commented on GitHub (Feb 3, 2020): Closing due to inactivity. Please reopen if symptoms persist.

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@Wang-Kai commented on GitHub (May 15, 2020):

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 .

@Wang-Kai commented on GitHub (May 15, 2020): > 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 .