[GH-ISSUE #916] Wrong region configration should be error #523

New issue

Closed

opened 2026-03-04 01:46:21 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:46:21 +03:00

Owner

Originally created by @ggtakec on GitHub (Jan 21, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/916

Version of s3fs being used (s3fs --version)

1.84

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

n/a

Kernel information (uname -r)

n/a(all)

GNU/Linux Distribution, if applicable (cat /etc/os-release)

n/a(all)

s3fs command line used, if applicable

n/a

/etc/fstab entry, if applicable

n/a

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

n/a

Details about issue

In the connection error with the configuration specifying the wrong region, the endpoint is automatically switched to the correct region by #912 modification.
But s3fs should not use this way, it should display explicitly error and stop to run.

Please see detail in #912 and #807

#807 #912

Originally created by @ggtakec on GitHub (Jan 21, 2019). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/916 #### Version of s3fs being used (s3fs --version) 1.84 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) n/a #### Kernel information (uname -r) n/a(all) #### GNU/Linux Distribution, if applicable (cat /etc/os-release) n/a(all) #### s3fs command line used, if applicable n/a #### /etc/fstab entry, if applicable n/a #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) n/a ### Details about issue In the connection error with the configuration specifying the wrong region, the endpoint is automatically switched to the correct region by #912 modification. But s3fs should not use this way, it should display explicitly error and stop to run. Please see detail in #912 and #807 #### Related issue etc. #807 #912

kerem closed this issue

2026-03-04 01:46:21 +03:00

kerem commented

2026-03-04 01:46:22 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 23, 2019):

I receive the opinions of @sqlbot ( https://github.com/s3fs-fuse/s3fs-fuse/pull/912#issuecomment-455875219 ) and @tbooth ( https://github.com/s3fs-fuse/s3fs-fuse/pull/912#issuecomment-456162930 ), and I will fix s3fs to retry in order to bypass the error in case of the default region(a case of that user does not specify endpoint).
This is the same as before (before modification of #912).
When retrying, a message indicating retrying is displayed.
If it is an error about different region and s3fs does not retry, it outputs the correct endpoint and url options and urges the retry.

@ggtakec commented on GitHub (Jan 23, 2019): I receive the opinions of @sqlbot ( https://github.com/s3fs-fuse/s3fs-fuse/pull/912#issuecomment-455875219 ) and @tbooth ( https://github.com/s3fs-fuse/s3fs-fuse/pull/912#issuecomment-456162930 ), and I will fix s3fs to retry in order to bypass the error in case of the default region(a case of that user does not specify endpoint). This is the same as before (before modification of #912). When retrying, a message indicating retrying is displayed. If it is an error about different region and s3fs does not retry, it outputs the correct endpoint and url options and urges the retry.

kerem commented

2026-03-04 01:46:22 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 23, 2019):

I close tihis issue, if you found a problem about this, please reopen.

@ggtakec commented on GitHub (Jan 23, 2019): I close tihis issue, if you found a problem about this, please reopen.

kerem referenced this issue

2026-03-04 02:00:56 +03:00

[PR #545] [MERGED] Changed base cached time of stat_cache_expire option - #523 #1539