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 #210] Random dismount on S3 #120

New issue

Closed

opened 2026-03-04 01:42:17 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 01:42:17 +03:00

Owner

Originally created by @drsku on GitHub (Jul 17, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/210

Our S3 bucket mounted on EC2 randomly dismounted on our first day of going live on AWS. We weren't doing anything special as far as we know. Our web site therefore went down... bit of downer.

Anyone got any suggestions to avoid this happening in the future, or know any common causes of this behaviour.

Thanks
Dan

Originally created by @drsku on GitHub (Jul 17, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/210 Our S3 bucket mounted on EC2 randomly dismounted on our first day of going live on AWS. We weren't doing anything special as far as we know. Our web site therefore went down... bit of downer. Anyone got any suggestions to avoid this happening in the future, or know any common causes of this behaviour. Thanks Dan

kerem closed this issue

2026-03-04 01:42:17 +03:00

kerem commented

2026-03-04 01:42:18 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 17, 2016):

I'm sorry for that this issue had been left at a long period of time.

Could you run s3fs with dbglevel(and curldbg if you need)?
This option let s3fs put debug log into syslog(or displaying messages), thus the log helps us to solve this issue.

Thanks in advance for your assistance.

@ggtakec commented on GitHub (Jan 17, 2016): I'm sorry for that this issue had been left at a long period of time. Could you run s3fs with dbglevel(and curldbg if you need)? This option let s3fs put debug log into syslog(or displaying messages), thus the log helps us to solve this issue. Thanks in advance for your assistance.

kerem commented

2026-03-04 01:42:18 +03:00

Author

Owner

@pete-robinson commented on GitHub (Mar 29, 2017):

Hi @ggtakec,
We are experiencing this issue too. This happens completely at random with seemingly no trigger. When trying to LS the directory, the error we get when this happens is 'Transport endpoint not connected'.

The s3fs instance is mounted with:
sudo s3fs -o allow_other {bucket-name} {destination-directory}

As far as I'm aware, s3fs isn't producing any log files - is there a way to enable logging?

Regards
Pete

@pete-robinson commented on GitHub (Mar 29, 2017): Hi @ggtakec, We are experiencing this issue too. This happens completely at random with seemingly no trigger. When trying to LS the directory, the error we get when this happens is 'Transport endpoint not connected'. The s3fs instance is mounted with: `sudo s3fs -o allow_other {bucket-name} {destination-directory}` As far as I'm aware, s3fs isn't producing any log files - is there a way to enable logging? Regards Pete

kerem commented

2026-03-04 01:42:18 +03:00

Author

Owner

@gaul commented on GitHub (Mar 29, 2017):

@pete-robinson Run s3fs with -f -d (foreground, debug).

@gaul commented on GitHub (Mar 29, 2017): @pete-robinson Run s3fs with `-f -d` (foreground, debug).

kerem commented

2026-03-04 01:42:18 +03:00

Author

Owner

@ggtakec commented on GitHub (Apr 9, 2017):

@drsku @pete-robinson
When this problem occurs, is the s3fs process abnormally terminated?
If it ends abnormally, I think that we can identify the cause early if you know the status of the stack from the core file at that time.
And if you can, please try to use latest codes in master branch.

Thanks in advance for your help.

@ggtakec commented on GitHub (Apr 9, 2017): @drsku @pete-robinson When this problem occurs, is the s3fs process abnormally terminated? If it ends abnormally, I think that we can identify the cause early if you know the status of the stack from the core file at that time. And if you can, please try to use latest codes in master branch. Thanks in advance for your help.

kerem commented

2026-03-04 01:42:18 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 30, 2019):

We kept this issue open for a long time.
We launch new version 1.86, which fixed some problem(bugs).
Please use the latest version.
I will close this, but if the problem persists, please reopen or post a new issue.

@ggtakec commented on GitHub (Mar 30, 2019): We kept this issue open for a long time. We launch new version 1.86, which fixed some problem(bugs). Please use the latest version. I will close this, but if the problem persists, please reopen or post a new issue.