[GH-ISSUE #1889] s3fs: unexpected error from stat(). #958

Closed
opened 2026-03-04 01:50:14 +03:00 by kerem · 8 comments
Owner

Originally created by @freetec1 on GitHub (Feb 14, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1889

Additional Information

Version of s3fs being used (s3fs --version)

1.90

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

2.9.7

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

NAME="Ubuntu"
VERSION="18.04.6 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.6 LTS"
VERSION_ID="18.04"
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"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

s3fs command line used, if applicable

sudo s3fs bucketname /mnt/raw_storage/

Details about issue

Hello,

if i try to mount the s3 bucket with the given line i just get the error "s3fs: unexpected error from stat()". The mountpoint does exist and if i check the connection to s3 via

aws s3 ls s3://bucketname

i can see every file from the bucket.

Can somebody help me figure out the problem? Do you need any additional information.

Kind regards

Originally created by @freetec1 on GitHub (Feb 14, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1889 ### Additional Information #### Version of s3fs being used (s3fs --version) 1.90 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) 2.9.7 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) NAME="Ubuntu" VERSION="18.04.6 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.6 LTS" VERSION_ID="18.04" 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" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic #### s3fs command line used, if applicable ``` sudo s3fs bucketname /mnt/raw_storage/ ``` ### Details about issue Hello, if i try to mount the s3 bucket with the given line i just get the error "s3fs: unexpected error from stat()". The mountpoint does exist and if i check the connection to s3 via ``` aws s3 ls s3://bucketname ``` i can see every file from the bucket. Can somebody help me figure out the problem? Do you need any additional information. Kind regards
kerem closed this issue 2026-03-04 01:50:14 +03:00
Author
Owner

@joetex commented on GitHub (Feb 15, 2022):

We are seeing this issue as well.

error s3fs: unexpected error from stat().

Was there a new release recently? We automate the setup in Docker, and this occurred after pushing a code update.

The dockerfile clones from the master branch. I'm going to try changing it to target the 1.9.0 release instead, hopefully this helps.

EDIT: Definitely something up with the latest commits from within the last week. I'll keep using v1.90 tag until new release. Thanks.

<!-- gh-comment-id:1040879321 --> @joetex commented on GitHub (Feb 15, 2022): We are seeing this issue as well. ``` error s3fs: unexpected error from stat(). ``` Was there a new release recently? We automate the setup in Docker, and this occurred after pushing a code update. The dockerfile clones from the master branch. I'm going to try changing it to target the 1.9.0 release instead, hopefully this helps. EDIT: Definitely something up with the latest commits from within the last week. I'll keep using v1.90 tag until new release. Thanks.
Author
Owner

@mcaidans commented on GitHub (Feb 17, 2022):

Bumping, same issue, no change to code or our automatic deployment. Our last successful deploy was 16 days ago, and failed yesterday, so some change between those two times on the master branch caused the issue.

Solution for now is switching to 1.9.0 as already stated.

<!-- gh-comment-id:1042510807 --> @mcaidans commented on GitHub (Feb 17, 2022): Bumping, same issue, no change to code or our automatic deployment. Our last successful deploy was 16 days ago, and failed yesterday, so some change between those two times on the master branch caused the issue. Solution for now is switching to 1.9.0 as already stated.
Author
Owner

@ggtakec commented on GitHub (Feb 19, 2022):

@joetex @mcaidans Thanks for your bug reports.
I think this error is a bug fixed in # 1896.
(After this fix, I have another fix now)
Please try again with the latest master code.

<!-- gh-comment-id:1045980742 --> @ggtakec commented on GitHub (Feb 19, 2022): @joetex @mcaidans Thanks for your bug reports. I think this error is a bug fixed in # 1896. (After this fix, I have another fix now) Please try again with the latest master code.
Author
Owner

@bhoov commented on GitHub (Jan 31, 2023):

I'm getting this same error after a fresh brew install gromgit/fuse/s3fs-mac (which downloads s3fs version 1.9.1). The command:

s3fs BUCKET /PATH/TO/MOUNT -o url=ENDPOINT -o passwd_file=~/.passwd-s3fs

results in

s3fs: unexpected error from stat(~/.passwd-s3fs)

I am using M1 MacBook Ventura 13.0.1.

<!-- gh-comment-id:1410798091 --> @bhoov commented on GitHub (Jan 31, 2023): I'm getting this same error after a fresh `brew install gromgit/fuse/s3fs-mac` (which downloads `s3fs` version 1.9.1). The command: ``` s3fs BUCKET /PATH/TO/MOUNT -o url=ENDPOINT -o passwd_file=~/.passwd-s3fs ``` results in ``` s3fs: unexpected error from stat(~/.passwd-s3fs) ``` I am using M1 MacBook Ventura 13.0.1.
Author
Owner

@ggtakec commented on GitHub (Feb 12, 2023):

I think this bug has been fixed in master, so I will close this issue.
If you still have problems with the master code, please reopen it.

<!-- gh-comment-id:1426933229 --> @ggtakec commented on GitHub (Feb 12, 2023): I think this bug has been fixed in master, so I will close this issue. If you still have problems with the master code, please reopen it.
Author
Owner

@Yaski commented on GitHub (Mar 18, 2023):

Still has this error
s3fs version 1.91

<!-- gh-comment-id:1474678679 --> @Yaski commented on GitHub (Mar 18, 2023): Still has this error s3fs version 1.91
Author
Owner

@lvZic commented on GitHub (Apr 20, 2023):

still error

fixed @Yaski

Using absolute path of passwd_file (eg: /Usr/jacky/.passwd-s3fs) instead of "~ /.passwd-s3fs" fixed this error "s3fs: unexpected error from stat(~/.passwd-s3fs)".

<!-- gh-comment-id:1515854702 --> @lvZic commented on GitHub (Apr 20, 2023): ### still error fixed @Yaski Using absolute path of passwd_file (eg: /Usr/jacky/.passwd-s3fs) instead of "~ /.passwd-s3fs" fixed this error "s3fs: unexpected error from stat(~/.passwd-s3fs)".
Author
Owner

@papanito commented on GitHub (Apr 21, 2023):

You can also use $HOME instead of ~

<!-- gh-comment-id:1517802052 --> @papanito commented on GitHub (Apr 21, 2023): You can also use `$HOME` instead of `~`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#958
No description provided.