[GH-ISSUE #830] s3fs issue #483

New issue

Closed

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

kerem commented

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

Owner

Originally created by @dailong on GitHub (Sep 25, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/830

when I run s3fs test /mnt/s3 -o passwd_file=/.passwd-s3fs,
Then I run mount:
s3fs on /mnt/s3 type fuse.s3fs (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
Seems to have worked.
But in a few seconds, I run mount found it unmounted. why? Thank you

Originally created by @dailong on GitHub (Sep 25, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/830 when I run s3fs test /mnt/s3 -o passwd_file=~/.passwd-s3fs, Then I run mount: s3fs on /mnt/s3 type fuse.s3fs (rw,nosuid,nodev,relatime,user_id=0,group_id=0) Seems to have worked. But in a few seconds, I run mount found it unmounted. why? Thank you~

kerem closed this issue

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

kerem commented

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

Author

Owner

@gaul commented on GitHub (Jan 26, 2019):

Could you try running in the foreground via:

s3fs test /mnt/s3 -o passwd_file=/.passwd-s3fs -f

It looks like s3fs has exited and you don't see the error message since it is in the background.

@gaul commented on GitHub (Jan 26, 2019): Could you try running in the foreground via: ``` s3fs test /mnt/s3 -o passwd_file=/.passwd-s3fs -f ``` It looks like s3fs has exited and you don't see the error message since it is in the background.

kerem commented

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

Author

Owner

@gaul commented on GitHub (Apr 9, 2019):

Closing due to inactivity. Please reopen if symptoms persist.

@gaul commented on GitHub (Apr 9, 2019): Closing due to inactivity. Please reopen if symptoms persist.

kerem referenced this issue

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

[PR #483] [MERGED] Trim symbolic link original path in file. #1518