[GH-ISSUE #1943] Unable to list directory contents unless listing the full path to a file #980

Open
opened 2026-03-04 01:50:24 +03:00 by kerem · 9 comments
Owner

Originally created by @JossWhittle on GitHub (May 11, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1943

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD

Version of s3fs being used (s3fs --version)

1.91

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

2.9.9-3

Kernel information (uname -r)

5.4.0-104-generic

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

Ubuntu 20.04 LTS

s3fs command line used, if applicable

sudo s3fs -o url=https://s3.example.com,passwd_file=/etc/passwd-s3fs,ssl_verify_hostname=0,allow_other,notsup_compat_dir,sigv4,curldbg,listobjectsv2,umask=0000 rfi-hub-datasets:/mnt/ /ceph/echo/hub -d -f

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

Assume a local file system mount point /ceph/echo/hub.

And a remote s3 bucket rfi-hub-datasets:/mnt/ that contains a file rfi-hub-datasets:/mnt/world containing the text hello.


Listing the parent directory shows the mount point with a zeroed date stamp.

user@workstation:/ceph/echo$ll
total 9
drwxr-xr-x 3 root root 4096 May 10 21:53 ./
drwxr-xr-x 6 root root 4096 May  9 20:08 ../
drwxrwxrwx 1 root root    0 Jan  1  1970 hub/
2022-05-11T14:21:41.036Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/]

Listing the mount point directory shows no contents. [ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty. is reported.

user@workstation:/ceph/echo$ll hub
total 5
drwxrwxrwx 1 root root    0 Jan  1  1970 ./
drwxr-xr-x 3 root root 4096 May 10 21:53 ../
2022-05-11T14:21:48.082Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/]
2022-05-11T14:21:48.085Z [INF] s3fs.cpp:s3fs_opendir(2514): [path=/][flags=0x18800]
2022-05-11T14:21:48.086Z [INF] s3fs.cpp:s3fs_readdir(2663): [path=/]
2022-05-11T14:21:48.087Z [INF]   s3fs.cpp:list_bucket(2707): [path=/]
2022-05-11T14:21:48.087Z [INF]       curl.cpp:ListBucketRequest(3522): [tpath=/]
2022-05-11T14:21:48.087Z [INF]       curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets?delimiter=/&list-type=2&max-keys=1000&prefix=mnt/
2022-05-11T14:21:48.087Z [INF]       curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com?delimiter=/&list-type=2&max-keys=1000&prefix=mnt/
2022-05-11T14:21:48.087Z [INF]       curl.cpp:insertV4Headers(2696): computing signature [GET] [/] [delimiter=/&list-type=2&max-keys=1000&prefix=mnt/] []
2022-05-11T14:21:48.087Z [INF]       curl_util.cpp:url_to_host(332): url is https://s3.example.com
2022-05-11T14:21:48.087Z [CURL DBG] * Connection 0 seems to be dead!
2022-05-11T14:21:48.087Z [CURL DBG] * Closing connection 0
2022-05-11T14:21:48.087Z [CURL DBG] * TLSv1.2 (OUT), TLS alert, close notify (256):
2022-05-11T14:21:48.089Z [CURL DBG] * Hostname rfi-hub-datasets.s3.example.com was found in DNS cache
2022-05-11T14:21:48.089Z [CURL DBG] *   Trying 192.168.0.100:443...
2022-05-11T14:21:48.089Z [CURL DBG] * TCP_NODELAY set
2022-05-11T14:21:48.090Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#1)
2022-05-11T14:21:48.101Z [CURL DBG] * successfully set certificate verify locations:
2022-05-11T14:21:48.101Z [CURL DBG] *   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
2022-05-11T14:21:48.101Z [CURL DBG] * SSL re-using session ID
2022-05-11T14:21:48.101Z [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1):
2022-05-11T14:21:48.106Z [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2):
2022-05-11T14:21:48.107Z [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20):
2022-05-11T14:21:48.107Z [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
2022-05-11T14:21:48.107Z [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20):
2022-05-11T14:21:48.107Z [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
2022-05-11T14:21:48.107Z [CURL DBG] * Server certificate:
2022-05-11T14:21:48.107Z [CURL DBG] *  subject: REDACTED
2022-05-11T14:21:48.107Z [CURL DBG] *  start date: Mar  7 00:00:00 2022 GMT
2022-05-11T14:21:48.107Z [CURL DBG] *  expire date: Mar  7 23:59:59 2023 GMT
2022-05-11T14:21:48.107Z [CURL DBG] *  issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4
2022-05-11T14:21:48.107Z [CURL DBG] *  SSL certificate verify ok.
2022-05-11T14:21:48.107Z [CURL DBG] > GET /?delimiter=/&list-type=2&max-keys=1000&prefix=mnt/ HTTP/1.1
2022-05-11T14:21:48.107Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com
2022-05-11T14:21:48.107Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL)
2022-05-11T14:21:48.107Z [CURL DBG] > Accept: */*
2022-05-11T14:21:48.107Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=9bb70409e7571a04e9517c7e2e1fd918e0fff91463930920364a309980d44f11
2022-05-11T14:21:48.107Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2022-05-11T14:21:48.107Z [CURL DBG] > x-amz-date: 20220511T142148Z
2022-05-11T14:21:48.107Z [CURL DBG] > 
2022-05-11T14:21:48.140Z [CURL DBG] * Mark bundle as not supporting multiuse
2022-05-11T14:21:48.140Z [CURL DBG] < HTTP/1.1 200 OK
2022-05-11T14:21:48.140Z [CURL DBG] < Transfer-Encoding: chunked
2022-05-11T14:21:48.140Z [CURL DBG] < x-amz-request-id: tx000000000000003fb4525-00627bc67c-218cd2a5a-default
2022-05-11T14:21:48.140Z [CURL DBG] < Content-Type: application/xml
2022-05-11T14:21:48.140Z [CURL DBG] < Date: Wed, 11 May 2022 14:21:48 GMT
2022-05-11T14:21:48.140Z [CURL DBG] < 
2022-05-11T14:21:48.141Z [CURL DBG] * Connection #1 to host rfi-hub-datasets.s3.example.com left intact
2022-05-11T14:21:48.141Z [INF]       curl.cpp:RequestPerform(2324): HTTP response code 200
2022-05-11T14:21:48.141Z [ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty.
2022-05-11T14:21:48.141Z [ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty.
2022-05-11T14:21:48.141Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/]

Listing the full file path hub/world returns the expected result for that specific file.

user@workstation:/ceph/echo$ll hub/world
-rwxrwxrwx 1 user user 6 May 10 22:09 hub/world*
2022-05-11T14:21:56.976Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/world]
2022-05-11T14:21:56.977Z [INF]       curl.cpp:HeadRequest(3100): [tpath=/world]
2022-05-11T14:21:56.977Z [INF]       curl.cpp:PreHeadRequest(3060): [tpath=/world][bpath=][save=][sseckeypos=18446744073709551615]
2022-05-11T14:21:56.977Z [INF]       curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets/mnt/world
2022-05-11T14:21:56.977Z [INF]       curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com/mnt/world
2022-05-11T14:21:56.977Z [INF]       curl.cpp:insertV4Headers(2696): computing signature [HEAD] [/mnt/world] [] []
2022-05-11T14:21:56.977Z [INF]       curl_util.cpp:url_to_host(332): url is https://s3.example.com
2022-05-11T14:21:56.978Z [CURL DBG] * Connection 1 seems to be dead!
2022-05-11T14:21:56.978Z [CURL DBG] * Closing connection 1
2022-05-11T14:21:56.978Z [CURL DBG] * TLSv1.2 (OUT), TLS alert, close notify (256):
2022-05-11T14:21:56.980Z [CURL DBG] * Hostname rfi-hub-datasets.s3.example.com was found in DNS cache
2022-05-11T14:21:56.980Z [CURL DBG] *   Trying 192.168.0.100:443...
2022-05-11T14:21:56.980Z [CURL DBG] * TCP_NODELAY set
2022-05-11T14:21:56.980Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#2)
2022-05-11T14:21:56.992Z [CURL DBG] * successfully set certificate verify locations:
2022-05-11T14:21:56.992Z [CURL DBG] *   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
2022-05-11T14:21:56.992Z [CURL DBG] * SSL re-using session ID
2022-05-11T14:21:56.992Z [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1):
2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2):
2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20):
2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20):
2022-05-11T14:21:56.997Z [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
2022-05-11T14:21:56.997Z [CURL DBG] * Server certificate:
2022-05-11T14:21:56.997Z [CURL DBG] *  subject: REDACTED
2022-05-11T14:21:56.997Z [CURL DBG] *  start date: Mar  7 00:00:00 2022 GMT
2022-05-11T14:21:56.997Z [CURL DBG] *  expire date: Mar  7 23:59:59 2023 GMT
2022-05-11T14:21:56.997Z [CURL DBG] *  issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4
2022-05-11T14:21:56.998Z [CURL DBG] *  SSL certificate verify ok.
2022-05-11T14:21:56.998Z [CURL DBG] > HEAD /mnt/world HTTP/1.1
2022-05-11T14:21:56.998Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com
2022-05-11T14:21:56.998Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL)
2022-05-11T14:21:56.998Z [CURL DBG] > Accept: */*
2022-05-11T14:21:56.998Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=51050872117178da5da03e1403fd14de4a8821f2bdec2e0e2e91ef3821149a78
2022-05-11T14:21:56.998Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2022-05-11T14:21:56.998Z [CURL DBG] > x-amz-date: 20220511T142156Z
2022-05-11T14:21:56.998Z [CURL DBG] > 
2022-05-11T14:21:57.031Z [CURL DBG] * Mark bundle as not supporting multiuse
2022-05-11T14:21:57.031Z [CURL DBG] < HTTP/1.1 200 OK
2022-05-11T14:21:57.031Z [CURL DBG] < Content-Length: 6
2022-05-11T14:21:57.031Z [CURL DBG] < Accept-Ranges: bytes
2022-05-11T14:21:57.031Z [CURL DBG] < Last-Modified: Tue, 10 May 2022 22:09:21 GMT
2022-05-11T14:21:57.031Z [CURL DBG] < x-rgw-object-type: Normal
2022-05-11T14:21:57.031Z [CURL DBG] < ETag: "b1946ac92492d2347c6235b4d2611184"
2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-atime: 1652220561
2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-ctime: 1652220561
2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-gid: 1217275
2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-mode: 33204
2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-mtime: 1652220561
2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-uid: 1217275
2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-request-id: tx000000000000003fb46b1-00627bc685-218cd2a5a-default
2022-05-11T14:21:57.031Z [CURL DBG] < Content-Type: application/octet-stream
2022-05-11T14:21:57.031Z [CURL DBG] < Date: Wed, 11 May 2022 14:21:57 GMT
2022-05-11T14:21:57.031Z [CURL DBG] < 
2022-05-11T14:21:57.031Z [CURL DBG] * Connection #2 to host rfi-hub-datasets.s3.example.com left intact
2022-05-11T14:21:57.031Z [INF]       curl.cpp:RequestPerform(2324): HTTP response code 200
2022-05-11T14:21:57.031Z [INF]       cache.cpp:AddStat(343): add stat cache entry[path=/world]

Cat'ing the full file path hub/world returns the expected file contents for that specific file.

user@workstation:/ceph/echo$cat hub/world
hello
2022-05-11T14:22:10.980Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/world]
2022-05-11T14:22:10.982Z [INF] s3fs.cpp:s3fs_open(2255): [path=/world][flags=0x8000]
2022-05-11T14:22:10.982Z [INF]       fdcache.cpp:GetFdEntity(485): [path=/world][pseudo_fd=-1]
2022-05-11T14:22:10.982Z [INF]       cache.cpp:DelStat(591): delete stat cache entry[path=/world]
2022-05-11T14:22:10.983Z [INF]       curl.cpp:HeadRequest(3100): [tpath=/world]
2022-05-11T14:22:10.983Z [INF]       curl.cpp:PreHeadRequest(3060): [tpath=/world][bpath=][save=][sseckeypos=18446744073709551615]
2022-05-11T14:22:10.983Z [INF]       curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets/mnt/world
2022-05-11T14:22:10.983Z [INF]       curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com/mnt/world
2022-05-11T14:22:10.983Z [INF]       curl.cpp:insertV4Headers(2696): computing signature [HEAD] [/mnt/world] [] []
2022-05-11T14:22:10.983Z [INF]       curl_util.cpp:url_to_host(332): url is https://s3.example.com
2022-05-11T14:22:10.983Z [CURL DBG] * Connection 2 seems to be dead!
2022-05-11T14:22:10.983Z [CURL DBG] * Closing connection 2
2022-05-11T14:22:10.983Z [CURL DBG] * TLSv1.2 (OUT), TLS alert, close notify (256):
2022-05-11T14:22:10.985Z [CURL DBG] * Hostname rfi-hub-datasets.s3.example.com was found in DNS cache
2022-05-11T14:22:10.985Z [CURL DBG] *   Trying 192.168.0.100:443...
2022-05-11T14:22:10.985Z [CURL DBG] * TCP_NODELAY set
2022-05-11T14:22:10.986Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#3)
2022-05-11T14:22:10.996Z [CURL DBG] * successfully set certificate verify locations:
2022-05-11T14:22:10.996Z [CURL DBG] *   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
2022-05-11T14:22:10.996Z [CURL DBG] * SSL re-using session ID
2022-05-11T14:22:10.996Z [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1):
2022-05-11T14:22:11.002Z [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2):
2022-05-11T14:22:11.002Z [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20):
2022-05-11T14:22:11.003Z [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
2022-05-11T14:22:11.003Z [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20):
2022-05-11T14:22:11.003Z [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
2022-05-11T14:22:11.003Z [CURL DBG] * Server certificate:
2022-05-11T14:22:11.003Z [CURL DBG] *  subject: REDACTED
2022-05-11T14:22:11.003Z [CURL DBG] *  start date: Mar  7 00:00:00 2022 GMT
2022-05-11T14:22:11.003Z [CURL DBG] *  expire date: Mar  7 23:59:59 2023 GMT
2022-05-11T14:22:11.003Z [CURL DBG] *  issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4
2022-05-11T14:22:11.003Z [CURL DBG] *  SSL certificate verify ok.
2022-05-11T14:22:11.003Z [CURL DBG] > HEAD /mnt/world HTTP/1.1
2022-05-11T14:22:11.003Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com
2022-05-11T14:22:11.003Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL)
2022-05-11T14:22:11.003Z [CURL DBG] > Accept: */*
2022-05-11T14:22:11.003Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2677b7f5119db8732830b4d295eb0c227f757452381e4b6d96502339b40deee9
2022-05-11T14:22:11.003Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2022-05-11T14:22:11.003Z [CURL DBG] > x-amz-date: 20220511T142210Z
2022-05-11T14:22:11.003Z [CURL DBG] > 
2022-05-11T14:22:11.036Z [CURL DBG] * Mark bundle as not supporting multiuse
2022-05-11T14:22:11.036Z [CURL DBG] < HTTP/1.1 200 OK
2022-05-11T14:22:11.036Z [CURL DBG] < Content-Length: 6
2022-05-11T14:22:11.036Z [CURL DBG] < Accept-Ranges: bytes
2022-05-11T14:22:11.036Z [CURL DBG] < Last-Modified: Tue, 10 May 2022 22:09:21 GMT
2022-05-11T14:22:11.036Z [CURL DBG] < x-rgw-object-type: Normal
2022-05-11T14:22:11.036Z [CURL DBG] < ETag: "b1946ac92492d2347c6235b4d2611184"
2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-atime: 1652220561
2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-ctime: 1652220561
2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-gid: 1217275
2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-mode: 33204
2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-mtime: 1652220561
2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-uid: 1217275
2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-request-id: tx000000000000003fb49d3-00627bc693-218cd2a5a-default
2022-05-11T14:22:11.036Z [CURL DBG] < Content-Type: application/octet-stream
2022-05-11T14:22:11.036Z [CURL DBG] < Date: Wed, 11 May 2022 14:22:11 GMT
2022-05-11T14:22:11.036Z [CURL DBG] < 
2022-05-11T14:22:11.036Z [CURL DBG] * Connection #3 to host rfi-hub-datasets.s3.example.com left intact
2022-05-11T14:22:11.036Z [INF]       curl.cpp:RequestPerform(2324): HTTP response code 200
2022-05-11T14:22:11.036Z [INF]       cache.cpp:AddStat(343): add stat cache entry[path=/world]
2022-05-11T14:22:11.039Z [INF]       fdcache_entity.cpp:SetMCtime(778): [path=/world][physical_fd=10][mtime=1652220561][ctime=1652220561]
2022-05-11T14:22:11.039Z [INF]       curl.cpp:GetObjectRequest(3443): [tpath=/world][start=0][size=6]
2022-05-11T14:22:11.039Z [INF]       curl.cpp:PreGetObjectRequest(3391): [tpath=/world][start=0][size=6]
2022-05-11T14:22:11.039Z [INF]       curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets/mnt/world
2022-05-11T14:22:11.039Z [INF]       curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com/mnt/world
2022-05-11T14:22:11.039Z [INF]       curl.cpp:GetObjectRequest(3462): downloading... [path=/world][fd=10]
2022-05-11T14:22:11.039Z [INF]       curl.cpp:insertV4Headers(2696): computing signature [GET] [/mnt/world] [] []
2022-05-11T14:22:11.039Z [INF]       curl_util.cpp:url_to_host(332): url is https://s3.example.com
2022-05-11T14:22:11.039Z [CURL DBG] * Found bundle for host rfi-hub-datasets.s3.example.com: 0x7fc0080b1410 [serially]
2022-05-11T14:22:11.039Z [CURL DBG] * Can not multiplex, even if we wanted to!
2022-05-11T14:22:11.039Z [CURL DBG] * Re-using existing connection! (#3) with host rfi-hub-datasets.s3.example.com
2022-05-11T14:22:11.039Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#3)
2022-05-11T14:22:11.040Z [CURL DBG] > GET /mnt/world HTTP/1.1
2022-05-11T14:22:11.040Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com
2022-05-11T14:22:11.040Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL)
2022-05-11T14:22:11.040Z [CURL DBG] > Accept: */*
2022-05-11T14:22:11.040Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;range;x-amz-content-sha256;x-amz-date, Signature=905355d24f0c6af99978bbb120813157f417876627cb78fea2265c9c60bb2f2d
2022-05-11T14:22:11.040Z [CURL DBG] > Range: bytes=0-5
2022-05-11T14:22:11.040Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2022-05-11T14:22:11.040Z [CURL DBG] > x-amz-date: 20220511T142211Z
2022-05-11T14:22:11.040Z [CURL DBG] > 
2022-05-11T14:22:11.066Z [CURL DBG] * Mark bundle as not supporting multiuse
2022-05-11T14:22:11.066Z [CURL DBG] < HTTP/1.1 206 Partial Content
2022-05-11T14:22:11.066Z [CURL DBG] < Content-Length: 6
2022-05-11T14:22:11.066Z [CURL DBG] < Content-Range: bytes 0-5/6
2022-05-11T14:22:11.066Z [CURL DBG] < Accept-Ranges: bytes
2022-05-11T14:22:11.066Z [CURL DBG] < Last-Modified: Tue, 10 May 2022 22:09:21 GMT
2022-05-11T14:22:11.066Z [CURL DBG] < x-rgw-object-type: Normal
2022-05-11T14:22:11.066Z [CURL DBG] < ETag: "b1946ac92492d2347c6235b4d2611184"
2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-atime: 1652220561
2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-ctime: 1652220561
2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-gid: 1217275
2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-mode: 33204
2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-mtime: 1652220561
2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-uid: 1217275
2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-request-id: tx000000000000003fb49d4-00627bc693-218cd2a5a-default
2022-05-11T14:22:11.066Z [CURL DBG] < Content-Type: application/octet-stream
2022-05-11T14:22:11.066Z [CURL DBG] < Date: Wed, 11 May 2022 14:22:11 GMT
2022-05-11T14:22:11.066Z [CURL DBG] < 
2022-05-11T14:22:11.067Z [CURL DBG] * Connection #3 to host rfi-hub-datasets.s3.example.com left intact
2022-05-11T14:22:11.067Z [INF]       curl.cpp:RequestPerform(2324): HTTP response code 206
2022-05-11T14:22:11.067Z [INF] s3fs.cpp:s3fs_flush(2409): [path=/world][pseudo_fd=2]
2022-05-11T14:22:11.068Z [INF]       fdcache_entity.cpp:RowFlush(1347): [tpath=][path=/world][pseudo_fd=2][physical_fd=10]
2022-05-11T14:22:11.068Z [INF]       cache.cpp:DelStat(591): delete stat cache entry[path=/world]
2022-05-11T14:22:11.068Z [INF] s3fs.cpp:s3fs_release(2467): [path=/world][pseudo_fd=2]
2022-05-11T14:22:11.068Z [INF]       fdcache.cpp:GetFdEntity(485): [path=/world][pseudo_fd=2]

Details about issue

The mount allows creating and removing files and directories, along with reading and writing file contents. But we cannot list the directory contents unless we specify the full path to a specific file.

Directory listing is possible on our ceph s3 cluster since we do this without issue using Boto3 and MinioMC.

This has also been tested without the listobjectsv2 option. The same exact behaviour is reported, although the request details in the logs are slightly different as is to be expected. The error [ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty. is the same in both cases.

Originally created by @JossWhittle on GitHub (May 11, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1943 ### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ _Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD_ #### Version of s3fs being used (s3fs --version) 1.91 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) 2.9.9-3 #### Kernel information (uname -r) 5.4.0-104-generic #### GNU/Linux Distribution, if applicable (cat /etc/os-release) Ubuntu 20.04 LTS #### s3fs command line used, if applicable ``` sudo s3fs -o url=https://s3.example.com,passwd_file=/etc/passwd-s3fs,ssl_verify_hostname=0,allow_other,notsup_compat_dir,sigv4,curldbg,listobjectsv2,umask=0000 rfi-hub-datasets:/mnt/ /ceph/echo/hub -d -f ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) Assume a local file system mount point `/ceph/echo/hub`. And a remote s3 bucket `rfi-hub-datasets:/mnt/` that contains a file `rfi-hub-datasets:/mnt/world` containing the text `hello`. --- #### Listing the parent directory shows the mount point with a zeroed date stamp. ``` user@workstation:/ceph/echo$ll total 9 drwxr-xr-x 3 root root 4096 May 10 21:53 ./ drwxr-xr-x 6 root root 4096 May 9 20:08 ../ drwxrwxrwx 1 root root 0 Jan 1 1970 hub/ ``` ``` 2022-05-11T14:21:41.036Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/] ``` --- #### Listing the mount point directory shows no contents. `[ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty.` is reported. ``` user@workstation:/ceph/echo$ll hub total 5 drwxrwxrwx 1 root root 0 Jan 1 1970 ./ drwxr-xr-x 3 root root 4096 May 10 21:53 ../ ``` ``` 2022-05-11T14:21:48.082Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/] 2022-05-11T14:21:48.085Z [INF] s3fs.cpp:s3fs_opendir(2514): [path=/][flags=0x18800] 2022-05-11T14:21:48.086Z [INF] s3fs.cpp:s3fs_readdir(2663): [path=/] 2022-05-11T14:21:48.087Z [INF] s3fs.cpp:list_bucket(2707): [path=/] 2022-05-11T14:21:48.087Z [INF] curl.cpp:ListBucketRequest(3522): [tpath=/] 2022-05-11T14:21:48.087Z [INF] curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets?delimiter=/&list-type=2&max-keys=1000&prefix=mnt/ 2022-05-11T14:21:48.087Z [INF] curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com?delimiter=/&list-type=2&max-keys=1000&prefix=mnt/ 2022-05-11T14:21:48.087Z [INF] curl.cpp:insertV4Headers(2696): computing signature [GET] [/] [delimiter=/&list-type=2&max-keys=1000&prefix=mnt/] [] 2022-05-11T14:21:48.087Z [INF] curl_util.cpp:url_to_host(332): url is https://s3.example.com 2022-05-11T14:21:48.087Z [CURL DBG] * Connection 0 seems to be dead! 2022-05-11T14:21:48.087Z [CURL DBG] * Closing connection 0 2022-05-11T14:21:48.087Z [CURL DBG] * TLSv1.2 (OUT), TLS alert, close notify (256): 2022-05-11T14:21:48.089Z [CURL DBG] * Hostname rfi-hub-datasets.s3.example.com was found in DNS cache 2022-05-11T14:21:48.089Z [CURL DBG] * Trying 192.168.0.100:443... 2022-05-11T14:21:48.089Z [CURL DBG] * TCP_NODELAY set 2022-05-11T14:21:48.090Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#1) 2022-05-11T14:21:48.101Z [CURL DBG] * successfully set certificate verify locations: 2022-05-11T14:21:48.101Z [CURL DBG] * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs 2022-05-11T14:21:48.101Z [CURL DBG] * SSL re-using session ID 2022-05-11T14:21:48.101Z [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1): 2022-05-11T14:21:48.106Z [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2): 2022-05-11T14:21:48.107Z [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20): 2022-05-11T14:21:48.107Z [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): 2022-05-11T14:21:48.107Z [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20): 2022-05-11T14:21:48.107Z [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 2022-05-11T14:21:48.107Z [CURL DBG] * Server certificate: 2022-05-11T14:21:48.107Z [CURL DBG] * subject: REDACTED 2022-05-11T14:21:48.107Z [CURL DBG] * start date: Mar 7 00:00:00 2022 GMT 2022-05-11T14:21:48.107Z [CURL DBG] * expire date: Mar 7 23:59:59 2023 GMT 2022-05-11T14:21:48.107Z [CURL DBG] * issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4 2022-05-11T14:21:48.107Z [CURL DBG] * SSL certificate verify ok. 2022-05-11T14:21:48.107Z [CURL DBG] > GET /?delimiter=/&list-type=2&max-keys=1000&prefix=mnt/ HTTP/1.1 2022-05-11T14:21:48.107Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com 2022-05-11T14:21:48.107Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL) 2022-05-11T14:21:48.107Z [CURL DBG] > Accept: */* 2022-05-11T14:21:48.107Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=9bb70409e7571a04e9517c7e2e1fd918e0fff91463930920364a309980d44f11 2022-05-11T14:21:48.107Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 2022-05-11T14:21:48.107Z [CURL DBG] > x-amz-date: 20220511T142148Z 2022-05-11T14:21:48.107Z [CURL DBG] > 2022-05-11T14:21:48.140Z [CURL DBG] * Mark bundle as not supporting multiuse 2022-05-11T14:21:48.140Z [CURL DBG] < HTTP/1.1 200 OK 2022-05-11T14:21:48.140Z [CURL DBG] < Transfer-Encoding: chunked 2022-05-11T14:21:48.140Z [CURL DBG] < x-amz-request-id: tx000000000000003fb4525-00627bc67c-218cd2a5a-default 2022-05-11T14:21:48.140Z [CURL DBG] < Content-Type: application/xml 2022-05-11T14:21:48.140Z [CURL DBG] < Date: Wed, 11 May 2022 14:21:48 GMT 2022-05-11T14:21:48.140Z [CURL DBG] < 2022-05-11T14:21:48.141Z [CURL DBG] * Connection #1 to host rfi-hub-datasets.s3.example.com left intact 2022-05-11T14:21:48.141Z [INF] curl.cpp:RequestPerform(2324): HTTP response code 200 2022-05-11T14:21:48.141Z [ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty. 2022-05-11T14:21:48.141Z [ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty. 2022-05-11T14:21:48.141Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/] ``` --- #### Listing the full file path `hub/world` returns the expected result for that specific file. ``` user@workstation:/ceph/echo$ll hub/world -rwxrwxrwx 1 user user 6 May 10 22:09 hub/world* ``` ``` 2022-05-11T14:21:56.976Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/world] 2022-05-11T14:21:56.977Z [INF] curl.cpp:HeadRequest(3100): [tpath=/world] 2022-05-11T14:21:56.977Z [INF] curl.cpp:PreHeadRequest(3060): [tpath=/world][bpath=][save=][sseckeypos=18446744073709551615] 2022-05-11T14:21:56.977Z [INF] curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets/mnt/world 2022-05-11T14:21:56.977Z [INF] curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com/mnt/world 2022-05-11T14:21:56.977Z [INF] curl.cpp:insertV4Headers(2696): computing signature [HEAD] [/mnt/world] [] [] 2022-05-11T14:21:56.977Z [INF] curl_util.cpp:url_to_host(332): url is https://s3.example.com 2022-05-11T14:21:56.978Z [CURL DBG] * Connection 1 seems to be dead! 2022-05-11T14:21:56.978Z [CURL DBG] * Closing connection 1 2022-05-11T14:21:56.978Z [CURL DBG] * TLSv1.2 (OUT), TLS alert, close notify (256): 2022-05-11T14:21:56.980Z [CURL DBG] * Hostname rfi-hub-datasets.s3.example.com was found in DNS cache 2022-05-11T14:21:56.980Z [CURL DBG] * Trying 192.168.0.100:443... 2022-05-11T14:21:56.980Z [CURL DBG] * TCP_NODELAY set 2022-05-11T14:21:56.980Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#2) 2022-05-11T14:21:56.992Z [CURL DBG] * successfully set certificate verify locations: 2022-05-11T14:21:56.992Z [CURL DBG] * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs 2022-05-11T14:21:56.992Z [CURL DBG] * SSL re-using session ID 2022-05-11T14:21:56.992Z [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1): 2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2): 2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20): 2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): 2022-05-11T14:21:56.997Z [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20): 2022-05-11T14:21:56.997Z [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 2022-05-11T14:21:56.997Z [CURL DBG] * Server certificate: 2022-05-11T14:21:56.997Z [CURL DBG] * subject: REDACTED 2022-05-11T14:21:56.997Z [CURL DBG] * start date: Mar 7 00:00:00 2022 GMT 2022-05-11T14:21:56.997Z [CURL DBG] * expire date: Mar 7 23:59:59 2023 GMT 2022-05-11T14:21:56.997Z [CURL DBG] * issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4 2022-05-11T14:21:56.998Z [CURL DBG] * SSL certificate verify ok. 2022-05-11T14:21:56.998Z [CURL DBG] > HEAD /mnt/world HTTP/1.1 2022-05-11T14:21:56.998Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com 2022-05-11T14:21:56.998Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL) 2022-05-11T14:21:56.998Z [CURL DBG] > Accept: */* 2022-05-11T14:21:56.998Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=51050872117178da5da03e1403fd14de4a8821f2bdec2e0e2e91ef3821149a78 2022-05-11T14:21:56.998Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 2022-05-11T14:21:56.998Z [CURL DBG] > x-amz-date: 20220511T142156Z 2022-05-11T14:21:56.998Z [CURL DBG] > 2022-05-11T14:21:57.031Z [CURL DBG] * Mark bundle as not supporting multiuse 2022-05-11T14:21:57.031Z [CURL DBG] < HTTP/1.1 200 OK 2022-05-11T14:21:57.031Z [CURL DBG] < Content-Length: 6 2022-05-11T14:21:57.031Z [CURL DBG] < Accept-Ranges: bytes 2022-05-11T14:21:57.031Z [CURL DBG] < Last-Modified: Tue, 10 May 2022 22:09:21 GMT 2022-05-11T14:21:57.031Z [CURL DBG] < x-rgw-object-type: Normal 2022-05-11T14:21:57.031Z [CURL DBG] < ETag: "b1946ac92492d2347c6235b4d2611184" 2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-atime: 1652220561 2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-ctime: 1652220561 2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-gid: 1217275 2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-mode: 33204 2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-mtime: 1652220561 2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-meta-uid: 1217275 2022-05-11T14:21:57.031Z [CURL DBG] < x-amz-request-id: tx000000000000003fb46b1-00627bc685-218cd2a5a-default 2022-05-11T14:21:57.031Z [CURL DBG] < Content-Type: application/octet-stream 2022-05-11T14:21:57.031Z [CURL DBG] < Date: Wed, 11 May 2022 14:21:57 GMT 2022-05-11T14:21:57.031Z [CURL DBG] < 2022-05-11T14:21:57.031Z [CURL DBG] * Connection #2 to host rfi-hub-datasets.s3.example.com left intact 2022-05-11T14:21:57.031Z [INF] curl.cpp:RequestPerform(2324): HTTP response code 200 2022-05-11T14:21:57.031Z [INF] cache.cpp:AddStat(343): add stat cache entry[path=/world] ``` --- #### Cat'ing the full file path `hub/world` returns the expected file contents for that specific file. ``` user@workstation:/ceph/echo$cat hub/world hello ``` ``` 2022-05-11T14:22:10.980Z [INF] s3fs.cpp:s3fs_getattr(763): [path=/world] 2022-05-11T14:22:10.982Z [INF] s3fs.cpp:s3fs_open(2255): [path=/world][flags=0x8000] 2022-05-11T14:22:10.982Z [INF] fdcache.cpp:GetFdEntity(485): [path=/world][pseudo_fd=-1] 2022-05-11T14:22:10.982Z [INF] cache.cpp:DelStat(591): delete stat cache entry[path=/world] 2022-05-11T14:22:10.983Z [INF] curl.cpp:HeadRequest(3100): [tpath=/world] 2022-05-11T14:22:10.983Z [INF] curl.cpp:PreHeadRequest(3060): [tpath=/world][bpath=][save=][sseckeypos=18446744073709551615] 2022-05-11T14:22:10.983Z [INF] curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets/mnt/world 2022-05-11T14:22:10.983Z [INF] curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com/mnt/world 2022-05-11T14:22:10.983Z [INF] curl.cpp:insertV4Headers(2696): computing signature [HEAD] [/mnt/world] [] [] 2022-05-11T14:22:10.983Z [INF] curl_util.cpp:url_to_host(332): url is https://s3.example.com 2022-05-11T14:22:10.983Z [CURL DBG] * Connection 2 seems to be dead! 2022-05-11T14:22:10.983Z [CURL DBG] * Closing connection 2 2022-05-11T14:22:10.983Z [CURL DBG] * TLSv1.2 (OUT), TLS alert, close notify (256): 2022-05-11T14:22:10.985Z [CURL DBG] * Hostname rfi-hub-datasets.s3.example.com was found in DNS cache 2022-05-11T14:22:10.985Z [CURL DBG] * Trying 192.168.0.100:443... 2022-05-11T14:22:10.985Z [CURL DBG] * TCP_NODELAY set 2022-05-11T14:22:10.986Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#3) 2022-05-11T14:22:10.996Z [CURL DBG] * successfully set certificate verify locations: 2022-05-11T14:22:10.996Z [CURL DBG] * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs 2022-05-11T14:22:10.996Z [CURL DBG] * SSL re-using session ID 2022-05-11T14:22:10.996Z [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1): 2022-05-11T14:22:11.002Z [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2): 2022-05-11T14:22:11.002Z [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20): 2022-05-11T14:22:11.003Z [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): 2022-05-11T14:22:11.003Z [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20): 2022-05-11T14:22:11.003Z [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 2022-05-11T14:22:11.003Z [CURL DBG] * Server certificate: 2022-05-11T14:22:11.003Z [CURL DBG] * subject: REDACTED 2022-05-11T14:22:11.003Z [CURL DBG] * start date: Mar 7 00:00:00 2022 GMT 2022-05-11T14:22:11.003Z [CURL DBG] * expire date: Mar 7 23:59:59 2023 GMT 2022-05-11T14:22:11.003Z [CURL DBG] * issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4 2022-05-11T14:22:11.003Z [CURL DBG] * SSL certificate verify ok. 2022-05-11T14:22:11.003Z [CURL DBG] > HEAD /mnt/world HTTP/1.1 2022-05-11T14:22:11.003Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com 2022-05-11T14:22:11.003Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL) 2022-05-11T14:22:11.003Z [CURL DBG] > Accept: */* 2022-05-11T14:22:11.003Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2677b7f5119db8732830b4d295eb0c227f757452381e4b6d96502339b40deee9 2022-05-11T14:22:11.003Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 2022-05-11T14:22:11.003Z [CURL DBG] > x-amz-date: 20220511T142210Z 2022-05-11T14:22:11.003Z [CURL DBG] > 2022-05-11T14:22:11.036Z [CURL DBG] * Mark bundle as not supporting multiuse 2022-05-11T14:22:11.036Z [CURL DBG] < HTTP/1.1 200 OK 2022-05-11T14:22:11.036Z [CURL DBG] < Content-Length: 6 2022-05-11T14:22:11.036Z [CURL DBG] < Accept-Ranges: bytes 2022-05-11T14:22:11.036Z [CURL DBG] < Last-Modified: Tue, 10 May 2022 22:09:21 GMT 2022-05-11T14:22:11.036Z [CURL DBG] < x-rgw-object-type: Normal 2022-05-11T14:22:11.036Z [CURL DBG] < ETag: "b1946ac92492d2347c6235b4d2611184" 2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-atime: 1652220561 2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-ctime: 1652220561 2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-gid: 1217275 2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-mode: 33204 2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-mtime: 1652220561 2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-meta-uid: 1217275 2022-05-11T14:22:11.036Z [CURL DBG] < x-amz-request-id: tx000000000000003fb49d3-00627bc693-218cd2a5a-default 2022-05-11T14:22:11.036Z [CURL DBG] < Content-Type: application/octet-stream 2022-05-11T14:22:11.036Z [CURL DBG] < Date: Wed, 11 May 2022 14:22:11 GMT 2022-05-11T14:22:11.036Z [CURL DBG] < 2022-05-11T14:22:11.036Z [CURL DBG] * Connection #3 to host rfi-hub-datasets.s3.example.com left intact 2022-05-11T14:22:11.036Z [INF] curl.cpp:RequestPerform(2324): HTTP response code 200 2022-05-11T14:22:11.036Z [INF] cache.cpp:AddStat(343): add stat cache entry[path=/world] 2022-05-11T14:22:11.039Z [INF] fdcache_entity.cpp:SetMCtime(778): [path=/world][physical_fd=10][mtime=1652220561][ctime=1652220561] 2022-05-11T14:22:11.039Z [INF] curl.cpp:GetObjectRequest(3443): [tpath=/world][start=0][size=6] 2022-05-11T14:22:11.039Z [INF] curl.cpp:PreGetObjectRequest(3391): [tpath=/world][start=0][size=6] 2022-05-11T14:22:11.039Z [INF] curl_util.cpp:prepare_url(255): URL is https://s3.example.com/rfi-hub-datasets/mnt/world 2022-05-11T14:22:11.039Z [INF] curl_util.cpp:prepare_url(288): URL changed is https://rfi-hub-datasets.s3.example.com/mnt/world 2022-05-11T14:22:11.039Z [INF] curl.cpp:GetObjectRequest(3462): downloading... [path=/world][fd=10] 2022-05-11T14:22:11.039Z [INF] curl.cpp:insertV4Headers(2696): computing signature [GET] [/mnt/world] [] [] 2022-05-11T14:22:11.039Z [INF] curl_util.cpp:url_to_host(332): url is https://s3.example.com 2022-05-11T14:22:11.039Z [CURL DBG] * Found bundle for host rfi-hub-datasets.s3.example.com: 0x7fc0080b1410 [serially] 2022-05-11T14:22:11.039Z [CURL DBG] * Can not multiplex, even if we wanted to! 2022-05-11T14:22:11.039Z [CURL DBG] * Re-using existing connection! (#3) with host rfi-hub-datasets.s3.example.com 2022-05-11T14:22:11.039Z [CURL DBG] * Connected to rfi-hub-datasets.s3.example.com (192.168.0.100) port 443 (#3) 2022-05-11T14:22:11.040Z [CURL DBG] > GET /mnt/world HTTP/1.1 2022-05-11T14:22:11.040Z [CURL DBG] > Host: rfi-hub-datasets.s3.example.com 2022-05-11T14:22:11.040Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash 49d92c7; OpenSSL) 2022-05-11T14:22:11.040Z [CURL DBG] > Accept: */* 2022-05-11T14:22:11.040Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=ACCESS_KEY_ID/20220511/us-east-1/s3/aws4_request, SignedHeaders=host;range;x-amz-content-sha256;x-amz-date, Signature=905355d24f0c6af99978bbb120813157f417876627cb78fea2265c9c60bb2f2d 2022-05-11T14:22:11.040Z [CURL DBG] > Range: bytes=0-5 2022-05-11T14:22:11.040Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 2022-05-11T14:22:11.040Z [CURL DBG] > x-amz-date: 20220511T142211Z 2022-05-11T14:22:11.040Z [CURL DBG] > 2022-05-11T14:22:11.066Z [CURL DBG] * Mark bundle as not supporting multiuse 2022-05-11T14:22:11.066Z [CURL DBG] < HTTP/1.1 206 Partial Content 2022-05-11T14:22:11.066Z [CURL DBG] < Content-Length: 6 2022-05-11T14:22:11.066Z [CURL DBG] < Content-Range: bytes 0-5/6 2022-05-11T14:22:11.066Z [CURL DBG] < Accept-Ranges: bytes 2022-05-11T14:22:11.066Z [CURL DBG] < Last-Modified: Tue, 10 May 2022 22:09:21 GMT 2022-05-11T14:22:11.066Z [CURL DBG] < x-rgw-object-type: Normal 2022-05-11T14:22:11.066Z [CURL DBG] < ETag: "b1946ac92492d2347c6235b4d2611184" 2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-atime: 1652220561 2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-ctime: 1652220561 2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-gid: 1217275 2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-mode: 33204 2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-mtime: 1652220561 2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-meta-uid: 1217275 2022-05-11T14:22:11.066Z [CURL DBG] < x-amz-request-id: tx000000000000003fb49d4-00627bc693-218cd2a5a-default 2022-05-11T14:22:11.066Z [CURL DBG] < Content-Type: application/octet-stream 2022-05-11T14:22:11.066Z [CURL DBG] < Date: Wed, 11 May 2022 14:22:11 GMT 2022-05-11T14:22:11.066Z [CURL DBG] < 2022-05-11T14:22:11.067Z [CURL DBG] * Connection #3 to host rfi-hub-datasets.s3.example.com left intact 2022-05-11T14:22:11.067Z [INF] curl.cpp:RequestPerform(2324): HTTP response code 206 2022-05-11T14:22:11.067Z [INF] s3fs.cpp:s3fs_flush(2409): [path=/world][pseudo_fd=2] 2022-05-11T14:22:11.068Z [INF] fdcache_entity.cpp:RowFlush(1347): [tpath=][path=/world][pseudo_fd=2][physical_fd=10] 2022-05-11T14:22:11.068Z [INF] cache.cpp:DelStat(591): delete stat cache entry[path=/world] 2022-05-11T14:22:11.068Z [INF] s3fs.cpp:s3fs_release(2467): [path=/world][pseudo_fd=2] 2022-05-11T14:22:11.068Z [INF] fdcache.cpp:GetFdEntity(485): [path=/world][pseudo_fd=2] ``` ### Details about issue The mount allows creating and removing files and directories, along with reading and writing file contents. But we cannot list the directory contents unless we specify the full path to a specific file. Directory listing is possible on our ceph s3 cluster since we do this without issue using Boto3 and MinioMC. This has also been tested without the `listobjectsv2` option. The same exact behaviour is reported, although the request details in the logs are slightly different as is to be expected. The error `[ERR] s3fs_xml.cpp:get_base_exp(110): marker_xp->nodesetval is empty.` is the same in both cases.
Author
Owner

@waewoo commented on GitHub (Jun 6, 2022):

Hi,

For information, we identify the same problem.

Regards

<!-- gh-comment-id:1147253528 --> @waewoo commented on GitHub (Jun 6, 2022): Hi, For information, we identify the same problem. Regards
Author
Owner

@gaul commented on GitHub (Jun 12, 2022):

I'm not sure what kind of directory structure you have that causes these symptoms -- can you show the ls output of AWS CLI, e.g.,

aws s3 ls s3://rfi-hub-datasets/ --recursive

I also note that you specified -o notsup_compat_dir -- can you try removing this?

<!-- gh-comment-id:1153164991 --> @gaul commented on GitHub (Jun 12, 2022): I'm not sure what kind of directory structure you have that causes these symptoms -- can you show the ls output of AWS CLI, e.g., ``` aws s3 ls s3://rfi-hub-datasets/ --recursive ``` I also note that you specified `-o notsup_compat_dir` -- can you try removing this?
Author
Owner

@JossWhittle commented on GitHub (Jun 13, 2022):

@gaul Hi, yes it produces the same result without this flag. Many combinations or arguments have been attempted all with the same behaviour.

Cheers,
Joss

<!-- gh-comment-id:1153812754 --> @JossWhittle commented on GitHub (Jun 13, 2022): @gaul Hi, yes it produces the same result without this flag. Many combinations or arguments have been attempted all with the same behaviour. Cheers, Joss
Author
Owner

@hereTac commented on GitHub (Dec 13, 2022):

Any news here? The same situtation here. Any solution for now? @JossWhittle @gaul @ggtakec

[root@3 mnt]# s3fs --version
Amazon Simple Storage Service File System V1.91 (commit:23a8124) with OpenSSL
<!-- gh-comment-id:1347640776 --> @hereTac commented on GitHub (Dec 13, 2022): Any news here? The same situtation here. Any solution for now? @JossWhittle @gaul @ggtakec ``` [root@3 mnt]# s3fs --version Amazon Simple Storage Service File System V1.91 (commit:23a8124) with OpenSSL ```
Author
Owner

@hereTac commented on GitHub (Dec 13, 2022):

Here is the log.
s3fs etloutput /mnt/s3test -o _netdev -o allow_other -o passwd_file=/root/.s3fs-etloutput -o use_path_request_style -o noatime -o parallel_count=10000 -o multipart_size=100 -o no_check_certificate -o max_write=131072 -o multireq_max=1000 -o mp_umask=000 -o umask=000 -o url=http://k8s.dc.xyz:19000 -o curldbg

Dec 13 10:57:50 3 s3fs[750268]:      add stat cache entry[path=/]
Dec 13 10:57:50 3 s3fs[750268]: curl.cpp:RequestPerform(2407): HEAD HTTP response code 400, returning EPERM.
Dec 13 10:57:50 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact
Dec 13 10:57:50 3 s3fs[750268]: <
Dec 13 10:57:50 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:51 GMT
Dec 13 10:57:50 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block
Dec 13 10:57:50 3 s3fs[750268]: < X-Content-Type-Options: nosniff
Dec 13 10:57:50 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF197219118
Dec 13 10:57:50 3 s3fs[750268]: < Vary: Accept-Encoding
Dec 13 10:57:50 3 s3fs[750268]: < Vary: Origin
Dec 13 10:57:50 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains
Dec 13 10:57:50 3 s3fs[750268]: < Server: MinIO
Dec 13 10:57:50 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content
Dec 13 10:57:50 3 s3fs[750268]: < Content-Length: 0
Dec 13 10:57:50 3 s3fs[750268]: < Accept-Ranges: bytes
Dec 13 10:57:50 3 s3fs[750268]: < HTTP/1.1 400 Bad Request
Dec 13 10:57:50 3 s3fs[750268]: >
Dec 13 10:57:50 3 s3fs[750268]: > x-amz-date: 20221213T025750Z
Dec 13 10:57:50 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 13 10:57:50 3 s3fs[750268]: > host: k8s.dc.xyz:19000
Dec 13 10:57:50 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=bd86a4dae92b2112b4f5e2b0d50252809eaddd8d398fd5ceb2e2670daf1600d4
Dec 13 10:57:50 3 s3fs[750268]: > Accept: */*
Dec 13 10:57:50 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL)
Dec 13 10:57:50 3 s3fs[750268]: > HEAD /etloutput// HTTP/1.1
Dec 13 10:57:50 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0)
Dec 13 10:57:50 3 s3fs[750268]: * Re-using existing connection! (#0) with host k8s.dc.xyz
Dec 13 10:57:50 3 s3fs[750268]: * Found bundle for host k8s.dc.xyz: 0x7f9e50018860
Dec 13 10:57:50 3 s3fs[750268]:      url is http://k8s.dc.xyz:19000
Dec 13 10:57:50 3 s3fs[750268]:      computing signature [HEAD] [//] [] []
Dec 13 10:57:50 3 s3fs[750268]:      URL changed is http://k8s.dc.xyz:19000/etloutput//
Dec 13 10:57:50 3 s3fs[750268]:      URL is http://k8s.dc.xyz:19000/etloutput//
Dec 13 10:57:50 3 s3fs[750268]:      [tpath=//][bpath=][save=][sseckeypos=18446744073709551615]
Dec 13 10:57:50 3 s3fs[750268]:      [tpath=//]
Dec 13 10:57:50 3 s3fs[750268]: [path=/]
Dec 13 10:57:50 3 systemd-logind: Removed session 38154431.
Dec 13 10:57:50 3 s3fs[750268]:      HTTP response code 200
Dec 13 10:57:50 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact
Dec 13 10:57:50 3 s3fs[750268]: <
Dec 13 10:57:50 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:50 GMT
Dec 13 10:57:50 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block
Dec 13 10:57:50 3 s3fs[750268]: < X-Content-Type-Options: nosniff
Dec 13 10:57:50 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF1502422BD
Dec 13 10:57:50 3 s3fs[750268]: < Vary: Accept-Encoding
Dec 13 10:57:50 3 s3fs[750268]: < Vary: Origin
Dec 13 10:57:50 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains
Dec 13 10:57:50 3 s3fs[750268]: < Server: MinIO
Dec 13 10:57:50 3 s3fs[750268]: < Content-Type: application/xml
Dec 13 10:57:50 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content
Dec 13 10:57:50 3 s3fs[750268]: < Content-Length: 403602
Dec 13 10:57:50 3 s3fs[750268]: < Accept-Ranges: bytes
Dec 13 10:57:50 3 s3fs[750268]: < HTTP/1.1 200 OK
Dec 13 10:57:49 3 s3fs[750268]: >
Dec 13 10:57:49 3 s3fs[750268]: > x-amz-date: 20221213T025749Z
Dec 13 10:57:49 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 13 10:57:49 3 s3fs[750268]: > host: k8s.dc.xyz:19000
Dec 13 10:57:49 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=9fe7fbb79c2d9c58495648794543a274125ea7d3db4b0b214b3059efc29ce7f9
Dec 13 10:57:49 3 s3fs[750268]: > Accept: */*
Dec 13 10:57:49 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL)
Dec 13 10:57:49 3 s3fs[750268]: > GET /etloutput/ HTTP/1.1
Dec 13 10:57:49 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0)
Dec 13 10:57:49 3 s3fs[750268]: *   Trying 172.25.52.45...
Dec 13 10:57:49 3 s3fs[750268]: * About to connect() to k8s.dc.xyz port 19000 (#0)
Dec 13 10:57:49 3 s3fs[750268]:      url is http://k8s.dc.xyz:19000
Dec 13 10:57:49 3 s3fs[750268]:      computing signature [GET] [/] [] []
Dec 13 10:57:49 3 s3fs[750268]:      URL changed is http://k8s.dc.xyz:19000/etloutput/
Dec 13 10:57:49 3 s3fs[750268]:      URL is http://k8s.dc.xyz:19000/etloutput/
Dec 13 10:57:49 3 s3fs[750268]: curl.cpp:ResetHandle(1841): The S3FS_CURLOPT_KEEP_SENDING_ON_ERROR option could not be set. For maximize performance you need to enable this option and you should use libcurl 7.51.0 or later.
Dec 13 10:57:49 3 s3fs[750268]: curl.cpp:ResetHandle(1838): The CURLOPT_SSL_ENABLE_ALPN option could not be unset. S3 server does not support ALPN, then this option should be disabled to maximize performance. you need to use libcurl 7.36.0 or later.
Dec 13 10:57:49 3 s3fs[750268]:      check a bucket.
Dec 13 10:57:49 3 s3fs[750268]: check services.
Dec 13 10:57:49 3 s3fs[750268]: init v1.91(commit:23a8124) with OpenSSL, credential-library(built-in)
Dec 13 10:57:49 3 s3fs[750268]: s3fs_cred.cpp:VersionS3fsCredential(60): Check why built-in function was called, the external credential library must have VersionS3fsCredential function.
Dec 13 10:57:49 3 s3fs[750261]:      Start worker thread in ThreadPoolMan.
Dec 13 10:57:49 3 s3fs[750261]:      Start worker thread in ThreadPoolMan.
Dec 13 10:57:49 3 s3fs[750261]:      Start worker thread in ThreadPoolMan.
Dec 13 10:57:49 3 s3fs[750261]:      Start worker thread in ThreadPoolMan.
Dec 13 10:57:49 3 s3fs[750261]:      Start worker thread in ThreadPoolMan.
Dec 13 10:57:49 3 s3fs[750261]: Any threads are running now, then nothing to do.
Dec 13 10:57:49 3 s3fs[750261]: The path to cache top dir is empty, thus not need to check permission.
Dec 13 10:57:49 3 s3fs[750261]: Loaded mime information from /etc/mime.types
Dec 13 10:57:49 3 s3fs[750261]:    PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
Dec 13 10:57:49 3 s3fs[750261]: s3fs_logger.cpp:LowSetLogLevel(239): change debug level from [CRT] to [INF]
Dec 13 10:57:49 3 s3fs[750261]: s3fs version 1.91(23a8124) : s3fs -o _netdev -o allow_other -o passwd_file=/root/.s3fs-etloutput -o use_path_request_style -o noatime -o parallel_count=10000 -o multipart_size=100 -o no_check_certificate -o max_write=131072 -o multireq_max=1000 -o mp_umask=000 -o umask=000 -o url=http://k8s.dc.xyz:19000 -o curldbg -o dbglevel=info etloutput /mnt/s3test

ll s3test/

Dec 13 10:57:57 3 s3fs[750268]:      HTTP response code 404 was returned, returning ENOENT
Dec 13 10:57:57 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact
Dec 13 10:57:57 3 s3fs[750268]: <
Dec 13 10:57:57 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:57 GMT
Dec 13 10:57:57 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block
Dec 13 10:57:57 3 s3fs[750268]: < X-Content-Type-Options: nosniff
Dec 13 10:57:57 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF31AF5E203
Dec 13 10:57:57 3 s3fs[750268]: < Vary: Accept-Encoding
Dec 13 10:57:57 3 s3fs[750268]: < Vary: Origin
Dec 13 10:57:57 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains
Dec 13 10:57:57 3 s3fs[750268]: < Server: MinIO
Dec 13 10:57:57 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content
Dec 13 10:57:57 3 s3fs[750268]: < Content-Length: 0
Dec 13 10:57:57 3 s3fs[750268]: < Accept-Ranges: bytes
Dec 13 10:57:57 3 s3fs[750268]: < HTTP/1.1 404 Not Found
Dec 13 10:57:57 3 s3fs[750268]: >
Dec 13 10:57:57 3 s3fs[750268]: > x-amz-date: 20221213T025757Z
Dec 13 10:57:57 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 13 10:57:57 3 s3fs[750268]: > host: k8s.dc.xyz:19000
Dec 13 10:57:57 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=7ec6e83ff2bb9a58f3ead80daf54c92bb6e39aa387f06b33bd5b88a4e2635ff7
Dec 13 10:57:57 3 s3fs[750268]: > Accept: */*
Dec 13 10:57:57 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL)
Dec 13 10:57:57 3 s3fs[750268]: > HEAD /etloutput/etl-dba4sqlaudit/ HTTP/1.1
Dec 13 10:57:57 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0)
Dec 13 10:57:57 3 s3fs[750268]: * Re-using existing connection! (#0) with host k8s.dc.xyz
Dec 13 10:57:57 3 s3fs[750268]: * Found bundle for host k8s.dc.xyz: 0x7f9e50018860
Dec 13 10:57:57 3 s3fs[750268]:      url is http://k8s.dc.xyz:19000
Dec 13 10:57:57 3 s3fs[750268]:      computing signature [HEAD] [/etl-dba4sqlaudit/] [] []
Dec 13 10:57:57 3 s3fs[750268]:      [count=1]
Dec 13 10:57:57 3 s3fs[750268]:      URL changed is http://k8s.dc.xyz:19000/etloutput/etl-dba4sqlaudit/
Dec 13 10:57:57 3 s3fs[750268]:      URL is http://k8s.dc.xyz:19000/etloutput/etl-dba4sqlaudit/
Dec 13 10:57:57 3 s3fs[750268]:      [tpath=/etl-dba4sqlaudit/][bpath=etl-dba4sqlaudit/][save=/etl-dba4sqlaudit/][sseckeypos=18446744073709551615]
Dec 13 10:57:57 3 s3fs[750268]:  [path=/][list=0]
Dec 13 10:57:57 3 s3fs[750268]:      HTTP response code 200
Dec 13 10:57:57 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact
Dec 13 10:57:57 3 s3fs[750268]: <
Dec 13 10:57:57 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:57 GMT
Dec 13 10:57:57 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block
Dec 13 10:57:57 3 s3fs[750268]: < X-Content-Type-Options: nosniff
Dec 13 10:57:57 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF31AAE2FCC
Dec 13 10:57:57 3 s3fs[750268]: < Vary: Accept-Encoding
Dec 13 10:57:57 3 s3fs[750268]: < Vary: Origin
Dec 13 10:57:57 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains
Dec 13 10:57:57 3 s3fs[750268]: < Server: MinIO
Dec 13 10:57:57 3 s3fs[750268]: < Content-Type: application/xml
Dec 13 10:57:57 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content
Dec 13 10:57:57 3 s3fs[750268]: < Content-Length: 326
Dec 13 10:57:57 3 s3fs[750268]: < Accept-Ranges: bytes
Dec 13 10:57:57 3 s3fs[750268]: < HTTP/1.1 200 OK
Dec 13 10:57:57 3 s3fs[750268]: >
Dec 13 10:57:57 3 s3fs[750268]: > x-amz-date: 20221213T025757Z
Dec 13 10:57:57 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 13 10:57:57 3 s3fs[750268]: > host: k8s.dc.xyz:19000
Dec 13 10:57:57 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=1753e0c2a353669c41b9553915a087980275a8c857a2fb693b5ed370e3ebfa53
Dec 13 10:57:57 3 s3fs[750268]: > Accept: */*
Dec 13 10:57:57 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL)
Dec 13 10:57:57 3 s3fs[750268]: > GET /etloutput/?delimiter=/&max-keys=1000&prefix= HTTP/1.1
Dec 13 10:57:57 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0)
Dec 13 10:57:57 3 s3fs[750268]: * Re-using existing connection! (#0) with host k8s.dc.xyz
Dec 13 10:57:57 3 s3fs[750268]: * Found bundle for host k8s.dc.xyz: 0x7f9e50018860
Dec 13 10:57:57 3 s3fs[750268]:      url is http://k8s.dc.xyz:19000
Dec 13 10:57:57 3 s3fs[750268]:      computing signature [GET] [/] [delimiter=/&max-keys=1000&prefix=] []
Dec 13 10:57:57 3 s3fs[750268]:      URL changed is http://k8s.dc.xyz:19000/etloutput/?delimiter=/&max-keys=1000&prefix=
Dec 13 10:57:57 3 s3fs[750268]:      URL is http://k8s.dc.xyz:19000/etloutput?delimiter=/&max-keys=1000&prefix=
Dec 13 10:57:57 3 s3fs[750268]:      [tpath=/]
Dec 13 10:57:57 3 s3fs[750268]:  [path=/]
Dec 13 10:57:57 3 s3fs[750268]: [path=/]
Dec 13 10:57:57 3 s3fs[750268]: [path=/][flags=0x18800]
Dec 13 10:57:57 3 s3fs[750268]: [path=/]
Dec 13 10:57:56 3 systemd: Started Session 38154442 of user tools.
Dec 13 10:57:56 3 systemd-logind: New session 38154442 of user tools.
Dec 13 10:57:56 3 s3fs[750268]: [path=/][mask=W_OK ]
Dec 13 10:57:56 3 s3fs[750268]: [path=/]

umount -l s3test/

Dec 13 10:58:05 3 kernel: s3fs[750268]: segfault at 7f9e58db79d0 ip 00007f9e5cda9f41 sp 00007ffc8026a3b0 error 4 in libpthread-2.17.so[7f9e5cda1000+17000]
Dec 13 10:58:05 3 s3fs[750268]: destroy
Dec 13 10:58:04 3 s3fs[750268]: [path=/]
<!-- gh-comment-id:1347663692 --> @hereTac commented on GitHub (Dec 13, 2022): Here is the log. `s3fs etloutput /mnt/s3test -o _netdev -o allow_other -o passwd_file=/root/.s3fs-etloutput -o use_path_request_style -o noatime -o parallel_count=10000 -o multipart_size=100 -o no_check_certificate -o max_write=131072 -o multireq_max=1000 -o mp_umask=000 -o umask=000 -o url=http://k8s.dc.xyz:19000 -o curldbg` ``` Dec 13 10:57:50 3 s3fs[750268]: add stat cache entry[path=/] Dec 13 10:57:50 3 s3fs[750268]: curl.cpp:RequestPerform(2407): HEAD HTTP response code 400, returning EPERM. Dec 13 10:57:50 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact Dec 13 10:57:50 3 s3fs[750268]: < Dec 13 10:57:50 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:51 GMT Dec 13 10:57:50 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block Dec 13 10:57:50 3 s3fs[750268]: < X-Content-Type-Options: nosniff Dec 13 10:57:50 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF197219118 Dec 13 10:57:50 3 s3fs[750268]: < Vary: Accept-Encoding Dec 13 10:57:50 3 s3fs[750268]: < Vary: Origin Dec 13 10:57:50 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains Dec 13 10:57:50 3 s3fs[750268]: < Server: MinIO Dec 13 10:57:50 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content Dec 13 10:57:50 3 s3fs[750268]: < Content-Length: 0 Dec 13 10:57:50 3 s3fs[750268]: < Accept-Ranges: bytes Dec 13 10:57:50 3 s3fs[750268]: < HTTP/1.1 400 Bad Request Dec 13 10:57:50 3 s3fs[750268]: > Dec 13 10:57:50 3 s3fs[750268]: > x-amz-date: 20221213T025750Z Dec 13 10:57:50 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 13 10:57:50 3 s3fs[750268]: > host: k8s.dc.xyz:19000 Dec 13 10:57:50 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=bd86a4dae92b2112b4f5e2b0d50252809eaddd8d398fd5ceb2e2670daf1600d4 Dec 13 10:57:50 3 s3fs[750268]: > Accept: */* Dec 13 10:57:50 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL) Dec 13 10:57:50 3 s3fs[750268]: > HEAD /etloutput// HTTP/1.1 Dec 13 10:57:50 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0) Dec 13 10:57:50 3 s3fs[750268]: * Re-using existing connection! (#0) with host k8s.dc.xyz Dec 13 10:57:50 3 s3fs[750268]: * Found bundle for host k8s.dc.xyz: 0x7f9e50018860 Dec 13 10:57:50 3 s3fs[750268]: url is http://k8s.dc.xyz:19000 Dec 13 10:57:50 3 s3fs[750268]: computing signature [HEAD] [//] [] [] Dec 13 10:57:50 3 s3fs[750268]: URL changed is http://k8s.dc.xyz:19000/etloutput// Dec 13 10:57:50 3 s3fs[750268]: URL is http://k8s.dc.xyz:19000/etloutput// Dec 13 10:57:50 3 s3fs[750268]: [tpath=//][bpath=][save=][sseckeypos=18446744073709551615] Dec 13 10:57:50 3 s3fs[750268]: [tpath=//] Dec 13 10:57:50 3 s3fs[750268]: [path=/] Dec 13 10:57:50 3 systemd-logind: Removed session 38154431. Dec 13 10:57:50 3 s3fs[750268]: HTTP response code 200 Dec 13 10:57:50 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact Dec 13 10:57:50 3 s3fs[750268]: < Dec 13 10:57:50 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:50 GMT Dec 13 10:57:50 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block Dec 13 10:57:50 3 s3fs[750268]: < X-Content-Type-Options: nosniff Dec 13 10:57:50 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF1502422BD Dec 13 10:57:50 3 s3fs[750268]: < Vary: Accept-Encoding Dec 13 10:57:50 3 s3fs[750268]: < Vary: Origin Dec 13 10:57:50 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains Dec 13 10:57:50 3 s3fs[750268]: < Server: MinIO Dec 13 10:57:50 3 s3fs[750268]: < Content-Type: application/xml Dec 13 10:57:50 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content Dec 13 10:57:50 3 s3fs[750268]: < Content-Length: 403602 Dec 13 10:57:50 3 s3fs[750268]: < Accept-Ranges: bytes Dec 13 10:57:50 3 s3fs[750268]: < HTTP/1.1 200 OK Dec 13 10:57:49 3 s3fs[750268]: > Dec 13 10:57:49 3 s3fs[750268]: > x-amz-date: 20221213T025749Z Dec 13 10:57:49 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 13 10:57:49 3 s3fs[750268]: > host: k8s.dc.xyz:19000 Dec 13 10:57:49 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=9fe7fbb79c2d9c58495648794543a274125ea7d3db4b0b214b3059efc29ce7f9 Dec 13 10:57:49 3 s3fs[750268]: > Accept: */* Dec 13 10:57:49 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL) Dec 13 10:57:49 3 s3fs[750268]: > GET /etloutput/ HTTP/1.1 Dec 13 10:57:49 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0) Dec 13 10:57:49 3 s3fs[750268]: * Trying 172.25.52.45... Dec 13 10:57:49 3 s3fs[750268]: * About to connect() to k8s.dc.xyz port 19000 (#0) Dec 13 10:57:49 3 s3fs[750268]: url is http://k8s.dc.xyz:19000 Dec 13 10:57:49 3 s3fs[750268]: computing signature [GET] [/] [] [] Dec 13 10:57:49 3 s3fs[750268]: URL changed is http://k8s.dc.xyz:19000/etloutput/ Dec 13 10:57:49 3 s3fs[750268]: URL is http://k8s.dc.xyz:19000/etloutput/ Dec 13 10:57:49 3 s3fs[750268]: curl.cpp:ResetHandle(1841): The S3FS_CURLOPT_KEEP_SENDING_ON_ERROR option could not be set. For maximize performance you need to enable this option and you should use libcurl 7.51.0 or later. Dec 13 10:57:49 3 s3fs[750268]: curl.cpp:ResetHandle(1838): The CURLOPT_SSL_ENABLE_ALPN option could not be unset. S3 server does not support ALPN, then this option should be disabled to maximize performance. you need to use libcurl 7.36.0 or later. Dec 13 10:57:49 3 s3fs[750268]: check a bucket. Dec 13 10:57:49 3 s3fs[750268]: check services. Dec 13 10:57:49 3 s3fs[750268]: init v1.91(commit:23a8124) with OpenSSL, credential-library(built-in) Dec 13 10:57:49 3 s3fs[750268]: s3fs_cred.cpp:VersionS3fsCredential(60): Check why built-in function was called, the external credential library must have VersionS3fsCredential function. Dec 13 10:57:49 3 s3fs[750261]: Start worker thread in ThreadPoolMan. Dec 13 10:57:49 3 s3fs[750261]: Start worker thread in ThreadPoolMan. Dec 13 10:57:49 3 s3fs[750261]: Start worker thread in ThreadPoolMan. Dec 13 10:57:49 3 s3fs[750261]: Start worker thread in ThreadPoolMan. Dec 13 10:57:49 3 s3fs[750261]: Start worker thread in ThreadPoolMan. Dec 13 10:57:49 3 s3fs[750261]: Any threads are running now, then nothing to do. Dec 13 10:57:49 3 s3fs[750261]: The path to cache top dir is empty, thus not need to check permission. Dec 13 10:57:49 3 s3fs[750261]: Loaded mime information from /etc/mime.types Dec 13 10:57:49 3 s3fs[750261]: PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) Dec 13 10:57:49 3 s3fs[750261]: s3fs_logger.cpp:LowSetLogLevel(239): change debug level from [CRT] to [INF] Dec 13 10:57:49 3 s3fs[750261]: s3fs version 1.91(23a8124) : s3fs -o _netdev -o allow_other -o passwd_file=/root/.s3fs-etloutput -o use_path_request_style -o noatime -o parallel_count=10000 -o multipart_size=100 -o no_check_certificate -o max_write=131072 -o multireq_max=1000 -o mp_umask=000 -o umask=000 -o url=http://k8s.dc.xyz:19000 -o curldbg -o dbglevel=info etloutput /mnt/s3test ``` `ll s3test/` ``` Dec 13 10:57:57 3 s3fs[750268]: HTTP response code 404 was returned, returning ENOENT Dec 13 10:57:57 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact Dec 13 10:57:57 3 s3fs[750268]: < Dec 13 10:57:57 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:57 GMT Dec 13 10:57:57 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block Dec 13 10:57:57 3 s3fs[750268]: < X-Content-Type-Options: nosniff Dec 13 10:57:57 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF31AF5E203 Dec 13 10:57:57 3 s3fs[750268]: < Vary: Accept-Encoding Dec 13 10:57:57 3 s3fs[750268]: < Vary: Origin Dec 13 10:57:57 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains Dec 13 10:57:57 3 s3fs[750268]: < Server: MinIO Dec 13 10:57:57 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content Dec 13 10:57:57 3 s3fs[750268]: < Content-Length: 0 Dec 13 10:57:57 3 s3fs[750268]: < Accept-Ranges: bytes Dec 13 10:57:57 3 s3fs[750268]: < HTTP/1.1 404 Not Found Dec 13 10:57:57 3 s3fs[750268]: > Dec 13 10:57:57 3 s3fs[750268]: > x-amz-date: 20221213T025757Z Dec 13 10:57:57 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 13 10:57:57 3 s3fs[750268]: > host: k8s.dc.xyz:19000 Dec 13 10:57:57 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=7ec6e83ff2bb9a58f3ead80daf54c92bb6e39aa387f06b33bd5b88a4e2635ff7 Dec 13 10:57:57 3 s3fs[750268]: > Accept: */* Dec 13 10:57:57 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL) Dec 13 10:57:57 3 s3fs[750268]: > HEAD /etloutput/etl-dba4sqlaudit/ HTTP/1.1 Dec 13 10:57:57 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0) Dec 13 10:57:57 3 s3fs[750268]: * Re-using existing connection! (#0) with host k8s.dc.xyz Dec 13 10:57:57 3 s3fs[750268]: * Found bundle for host k8s.dc.xyz: 0x7f9e50018860 Dec 13 10:57:57 3 s3fs[750268]: url is http://k8s.dc.xyz:19000 Dec 13 10:57:57 3 s3fs[750268]: computing signature [HEAD] [/etl-dba4sqlaudit/] [] [] Dec 13 10:57:57 3 s3fs[750268]: [count=1] Dec 13 10:57:57 3 s3fs[750268]: URL changed is http://k8s.dc.xyz:19000/etloutput/etl-dba4sqlaudit/ Dec 13 10:57:57 3 s3fs[750268]: URL is http://k8s.dc.xyz:19000/etloutput/etl-dba4sqlaudit/ Dec 13 10:57:57 3 s3fs[750268]: [tpath=/etl-dba4sqlaudit/][bpath=etl-dba4sqlaudit/][save=/etl-dba4sqlaudit/][sseckeypos=18446744073709551615] Dec 13 10:57:57 3 s3fs[750268]: [path=/][list=0] Dec 13 10:57:57 3 s3fs[750268]: HTTP response code 200 Dec 13 10:57:57 3 s3fs[750268]: * Connection #0 to host k8s.dc.xyz left intact Dec 13 10:57:57 3 s3fs[750268]: < Dec 13 10:57:57 3 s3fs[750268]: < Date: Tue, 13 Dec 2022 02:57:57 GMT Dec 13 10:57:57 3 s3fs[750268]: < X-Xss-Protection: 1; mode=block Dec 13 10:57:57 3 s3fs[750268]: < X-Content-Type-Options: nosniff Dec 13 10:57:57 3 s3fs[750268]: < X-Amz-Request-Id: 17303AF31AAE2FCC Dec 13 10:57:57 3 s3fs[750268]: < Vary: Accept-Encoding Dec 13 10:57:57 3 s3fs[750268]: < Vary: Origin Dec 13 10:57:57 3 s3fs[750268]: < Strict-Transport-Security: max-age=31536000; includeSubDomains Dec 13 10:57:57 3 s3fs[750268]: < Server: MinIO Dec 13 10:57:57 3 s3fs[750268]: < Content-Type: application/xml Dec 13 10:57:57 3 s3fs[750268]: < Content-Security-Policy: block-all-mixed-content Dec 13 10:57:57 3 s3fs[750268]: < Content-Length: 326 Dec 13 10:57:57 3 s3fs[750268]: < Accept-Ranges: bytes Dec 13 10:57:57 3 s3fs[750268]: < HTTP/1.1 200 OK Dec 13 10:57:57 3 s3fs[750268]: > Dec 13 10:57:57 3 s3fs[750268]: > x-amz-date: 20221213T025757Z Dec 13 10:57:57 3 s3fs[750268]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 13 10:57:57 3 s3fs[750268]: > host: k8s.dc.xyz:19000 Dec 13 10:57:57 3 s3fs[750268]: > Authorization: AWS4-HMAC-SHA256 Credential=etloutput/20221213/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=1753e0c2a353669c41b9553915a087980275a8c857a2fb693b5ed370e3ebfa53 Dec 13 10:57:57 3 s3fs[750268]: > Accept: */* Dec 13 10:57:57 3 s3fs[750268]: > User-Agent: s3fs/1.91 (commit hash 23a8124; OpenSSL) Dec 13 10:57:57 3 s3fs[750268]: > GET /etloutput/?delimiter=/&max-keys=1000&prefix= HTTP/1.1 Dec 13 10:57:57 3 s3fs[750268]: * Connected to k8s.dc.xyz (172.25.52.45) port 19000 (#0) Dec 13 10:57:57 3 s3fs[750268]: * Re-using existing connection! (#0) with host k8s.dc.xyz Dec 13 10:57:57 3 s3fs[750268]: * Found bundle for host k8s.dc.xyz: 0x7f9e50018860 Dec 13 10:57:57 3 s3fs[750268]: url is http://k8s.dc.xyz:19000 Dec 13 10:57:57 3 s3fs[750268]: computing signature [GET] [/] [delimiter=/&max-keys=1000&prefix=] [] Dec 13 10:57:57 3 s3fs[750268]: URL changed is http://k8s.dc.xyz:19000/etloutput/?delimiter=/&max-keys=1000&prefix= Dec 13 10:57:57 3 s3fs[750268]: URL is http://k8s.dc.xyz:19000/etloutput?delimiter=/&max-keys=1000&prefix= Dec 13 10:57:57 3 s3fs[750268]: [tpath=/] Dec 13 10:57:57 3 s3fs[750268]: [path=/] Dec 13 10:57:57 3 s3fs[750268]: [path=/] Dec 13 10:57:57 3 s3fs[750268]: [path=/][flags=0x18800] Dec 13 10:57:57 3 s3fs[750268]: [path=/] Dec 13 10:57:56 3 systemd: Started Session 38154442 of user tools. Dec 13 10:57:56 3 systemd-logind: New session 38154442 of user tools. Dec 13 10:57:56 3 s3fs[750268]: [path=/][mask=W_OK ] Dec 13 10:57:56 3 s3fs[750268]: [path=/] ``` `umount -l s3test/` ``` Dec 13 10:58:05 3 kernel: s3fs[750268]: segfault at 7f9e58db79d0 ip 00007f9e5cda9f41 sp 00007ffc8026a3b0 error 4 in libpthread-2.17.so[7f9e5cda1000+17000] Dec 13 10:58:05 3 s3fs[750268]: destroy Dec 13 10:58:04 3 s3fs[750268]: [path=/] ```
Author
Owner

@hereTac commented on GitHub (Dec 13, 2022):

In my opinion, after use s3fs mount bucket, ls return empty. Unless ls the full path file first, it will return the right floders. (As the Linux world, every thing is file, so as floders. Looks like s3fs-S3 is not , the file's full path is not treat as file? May be it just a bug.

<!-- gh-comment-id:1347874173 --> @hereTac commented on GitHub (Dec 13, 2022): In my opinion, after use s3fs mount bucket, `ls` return empty. Unless `ls` the full path file first, it will return the right floders. (As the Linux world, every thing is file, so as floders. Looks like s3fs-S3 is not , the file's full path is not treat as file? May be it just a bug.
Author
Owner

@ggtakec commented on GitHub (Jan 15, 2023):

I haven't been able to reproduce this issue yet.

I thought that @JossWhittle's report maight have been influenced by #2057.
However, it seems that this assumption is wrong because it is specified as rfi-hub-datasets:/mnt/

@hereTac uses V1.91 (commit:23a8124), so #2057 was already adapted.
So that it seems there is another reason, but I still haven't found why the problem is happening.

I may still be overlooking something.
If there's any information I should add, please let me know.

<!-- gh-comment-id:1383090619 --> @ggtakec commented on GitHub (Jan 15, 2023): I haven't been able to reproduce this issue yet. I thought that @JossWhittle's report maight have been influenced by #2057. However, it seems that this assumption is wrong because it is specified as `rfi-hub-datasets:/mnt/` @hereTac uses `V1.91 (commit:23a8124)`, so #2057 was already adapted. So that it seems there is another reason, but I still haven't found why the problem is happening. I may still be overlooking something. If there's any information I should add, please let me know.
Author
Owner

@gaul commented on GitHub (Sep 8, 2023):

Could you test again using 1.93?

<!-- gh-comment-id:1710965252 --> @gaul commented on GitHub (Sep 8, 2023): Could you test again using 1.93?
Author
Owner

@fidgetingbits commented on GitHub (Nov 1, 2023):

FWIW I ran into a similar issue on 1.92 today with all the same symptoms, and explicitly setting -ocompat_dir resulted in the folders showing up correctly.

<!-- gh-comment-id:1788709816 --> @fidgetingbits commented on GitHub (Nov 1, 2023): FWIW I ran into a similar issue on 1.92 today with all the same symptoms, and explicitly setting `-ocompat_dir` resulted in the folders showing up correctly.
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#980
No description provided.