[GH-ISSUE #845] s3fs client get worse,can't access some folder #492

New issue

Closed

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

kerem commented

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

Owner

Originally created by @marshalslee on GitHub (Oct 24, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/845

Additional Information

The endpoint is a ceph cluster

Version of s3fs being used (s3fs --version)

1.83_

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

example: 2.9.4

Kernel information (uname -r)

_command result: 3.10.0-693.el7.1.x86_64

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

_command result:
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

s3fs command line used, if applicable

s3fs -o no_check_certificate -o readwrite_timeout=300 -o use_path_request_style -o url=http://192.168.240.11:80 -o nomultipart -o nonempty -o nocopyapi -o allow_other -o passwd_file=/etc/passwd-s3fs-data 34e84ec6-d6a3-11e8-a36d-52540037e748 /usr/share/elasticsearch/s3

/etc/fstab entry, if applicable

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

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Details about issue

Elsticsearch can access all folder but only one /usr/share/elasticsearch/s3/nodes/0/indices/-jJycbZwS6G7p3yt1woFKQ/0/index.
So I try to umount ,but failed.
[root@es-34e84ec6-d6a3-11e8-a36d-52540037e748-db58874c8-zchd7 /]# umount
usr/share/elasticsearch/s3/
umount: /usr/share/elasticsearch/s3: target is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))

Originally created by @marshalslee on GitHub (Oct 24, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/845 ### Additional Information The endpoint is a ceph cluster #### Version of s3fs being used (s3fs --version) 1.83_ #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) _example: 2.9.4_ #### Kernel information (uname -r) _command result: 3.10.0-693.el7.1.x86_64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) _command result: NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" #### s3fs command line used, if applicable ``` s3fs -o no_check_certificate -o readwrite_timeout=300 -o use_path_request_style -o url=http://192.168.240.11:80 -o nomultipart -o nonempty -o nocopyapi -o allow_other -o passwd_file=/etc/passwd-s3fs-data 34e84ec6-d6a3-11e8-a36d-52540037e748 /usr/share/elasticsearch/s3 ``` #### /etc/fstab entry, if applicable ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` ``` ### Details about issue Elsticsearch can access all folder but only one /usr/share/elasticsearch/s3/nodes/0/indices/-jJycbZwS6G7p3yt1woFKQ/0/index. So I try to umount ,but failed. [root@es-34e84ec6-d6a3-11e8-a36d-52540037e748-db58874c8-zchd7 /]# umount usr/share/elasticsearch/s3/ umount: /usr/share/elasticsearch/s3: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))

kerem closed this issue

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

kerem commented

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

Author

Owner

@gaul commented on GitHub (Feb 2, 2019):

@marshalslee could you be more specific about your issue? Is it related to unmounting or something else? s3fs cannot unmount if an application has an open file descriptor to any file it manages. You can find out which process has an open fd via lsof. Stopping the process should allow umount to succeed.

@gaul commented on GitHub (Feb 2, 2019): @marshalslee could you be more specific about your issue? Is it related to unmounting or something else? s3fs cannot unmount if an application has an open file descriptor to any file it manages. You can find out which process has an open fd via `lsof`. Stopping the process should allow `umount` to succeed.

kerem commented

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

Author

Owner

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

Closing due to inactivity. Please open if symptoms persist.

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