Repository metrics
- Stars
- (7,799 stars)
- PR merge metrics
- (Avg merge 8d 1h) (10 merged PRs in 30d)
Description
Additional Information
Version of s3fs being used (s3fs --version)
V1.90 (commit:unknown)
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse or dpkg -s fuse)
No package 'fuse' found or similar, but S3FS works fine generally
Kernel information (uname -r)
6.2.0-39-generic
GNU/Linux Distribution, if applicable (cat /etc/os-release)
PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy
How to run s3fs, if applicable
[X] command line
[] /etc/fstab
s3fs <bucket name> <local empty dir> -o passwd_file=<password file> -o url=<OCI endpoint> -o use_path_request_style -o nonempty
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
Jan 11 13:10:51 yrden s3fs[720477]: s3fs version 1.90(unknown) : s3fs -o passwd_file=<password file> -o url=<OCI endpoint> -o use_path_request_style -o nonempty <bucket name> <local empty dir>
Jan 11 13:10:51 yrden s3fs[720477]: Loaded mime information from /etc/mime.types
Jan 11 13:10:51 yrden s3fs[720482]: init v1.90(commit:unknown) with GnuTLS(gcrypt)
Jan 11 13:10:53 yrden s3fs[720482]: s3fs.cpp:s3fs_check_service(3575): Failed to connect by sigv4, so retry to connect by signature version 2.
Jan 11 13:10:53 yrden s3fs[720482]: s3fs.cpp:s3fs_check_service(3587): Bad Request(host=<OCI endpoint>) - result of checking service.
Details about issue
If the password file (<password file> above) contains a valid but incorrect password, s3fs gives no indication of failure to mount. This has been tested with OCI's buckets - not sure if platform specific.
Cases which cause sensible 'failure to mount' errors (non-0 exitcode and a stderr message):
- Password file has permissions other than
600 - Password file contains whitespace
- Password file is not of correct format
Specific case this issue refers to which has an exitcode of 0 and no stderr message:
- Password file has correct permissions and formatting, but is functionally an incorrect password
Password file contents of access_key:not_real_key should replicate this behaviour. With a valid password file contents, the same command correctly mounts. Such a fail to mount should tell the user that the mount has failed.