[GH-ISSUE #1967] Getting error message The specified key does not exist while executing ls command from s3fs-fuse client #996

New issue

Open

opened 2026-03-04 01:50:30 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:50:30 +03:00

Owner

Originally created by @bhuvanp1305 on GitHub (Jun 23, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1967

Query

Please provide a detailed explanation of "ls" implementation in s3fs-fuse.

Version of s3fs being used (s3fs --version)

v1.91

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

example: 2.9.4

Kernel information (uname -r)

3.1.7-340.x86_64

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

command result: cat /etc/os-release

s3fs command line used, if applicable

/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

2022-06-23T10:00:12.521Z [CURL DBG] > HEAD /my-bucket/level-6/ HTTP/1.1
2022-06-23T10:00:12.521Z [CURL DBG] > Host: s3.openshift-storage:80
2022-06-23T10:00:12.521Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash unknown; OpenSSL)
2022-06-23T10:00:12.521Z [CURL DBG] > Accept: */*
2022-06-23T10:00:12.521Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=cwhl3ut6KMorHppPBtIH/20220623/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=32560b4da38f2372877db61350c63a0f2846d25b3881200a7e7a60838ec67207
2022-06-23T10:00:12.521Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2022-06-23T09:59:19.769Z [CURL DBG] * Connection #1 to host s3.openshift-storage left intact
2022-06-23T09:59:19.769Z [INF] curl.cpp:RequestPerform(2376): HTTP response code 404 was returned, returning ENOENT
2022-06-23T09:59:19.813Z [CURL DBG] < HTTP/1.1 404 Not Found
2022-06-23T09:59:19.813Z [CURL DBG] < x-amz-request-id: l4qurc28-v01aw-tnm
2022-06-23T09:59:19.813Z [CURL DBG] < x-amz-id-2: l4qurc28-v01aw-tnm
2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Origin: *
2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Credentials: true
2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Headers: Content-Type,Content-MD5,Authorization,X-Amz-User-Agent,X-Amz-Date,ETag,X-Amz-Content-Sha256
2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Expose-Headers: ETag,X-Amz-Version-Id
2022-06-23T09:59:19.813Z [CURL DBG] < Content-Type: application/xml
2022-06-23T09:59:19.813Z [CURL DBG] < Content-Length: 215
2022-06-23T09:59:19.813Z [CURL DBG] < Date: Thu, 23 Jun 2022 09:59:19 GMT
2022-06-23T09:59:19.813Z [CURL DBG] < Connection: keep-alive
2022-06-23T09:59:19.813Z [CURL DBG] < Keep-Alive: timeout=5
2022-06-23T09:59:19.813Z [CURL DBG] <

Details about issue

while executing ls command from s3fs-fuse client on mount path we error in debug mode also at the same time we are getting below error in s3 endpoint

Jun-23 10:00:12.541 [Endpoint/11] [ERROR] core.endpoint.s3.s3_rest:: S3 ERROR 
<?xml version="1.0" encoding="UTF-8"?><Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message>
<Resource>/my-bucket/level-6/</Resource><RequestId>l4qusgrz-djbgdn-15mm</RequestId>
</Error> HEAD /my-bucket/level-6/ {"host":"s3.openshift-storage:80","user-agent":"s3fs/1.91 (commit hash unknown; OpenSSL)","accept":"*/*","authorization":"AWS4-HMAC-SHA256 Credential=cwhl3ut6KMorHppPBtIH/20220623/us-east-1/s3/aws4_request, 
SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2ab2fad4ef3ec22c3fb78fa26151e61a37dbee887ac156f905c6f065fe34c95e","x-amz-content-sha256":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","x-amz-date":"20220623T100012Z"} 
[RpcError: No such object: obj_id undefined bucket SENSITIVE-d5bc0c9f50b30cee key level-8/] 
{ rpc_code: 'NO_SUCH_OBJECT' }

Originally created by @bhuvanp1305 on GitHub (Jun 23, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1967 ### Query Please provide a detailed explanation of "ls" implementation in s3fs-fuse. #### Version of s3fs being used (s3fs --version) v1.91 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) _example: 2.9.4_ #### Kernel information (uname -r) 3.1.7-340.x86_64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) _command result: cat /etc/os-release_ #### s3fs command line used, if applicable ``` ``` #### /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_ ``` 2022-06-23T10:00:12.521Z [CURL DBG] > HEAD /my-bucket/level-6/ HTTP/1.1 2022-06-23T10:00:12.521Z [CURL DBG] > Host: s3.openshift-storage:80 2022-06-23T10:00:12.521Z [CURL DBG] > User-Agent: s3fs/1.91 (commit hash unknown; OpenSSL) 2022-06-23T10:00:12.521Z [CURL DBG] > Accept: */* 2022-06-23T10:00:12.521Z [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=cwhl3ut6KMorHppPBtIH/20220623/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=32560b4da38f2372877db61350c63a0f2846d25b3881200a7e7a60838ec67207 2022-06-23T10:00:12.521Z [CURL DBG] > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 2022-06-23T09:59:19.769Z [CURL DBG] * Connection #1 to host s3.openshift-storage left intact 2022-06-23T09:59:19.769Z [INF] curl.cpp:RequestPerform(2376): HTTP response code 404 was returned, returning ENOENT 2022-06-23T09:59:19.813Z [CURL DBG] < HTTP/1.1 404 Not Found 2022-06-23T09:59:19.813Z [CURL DBG] < x-amz-request-id: l4qurc28-v01aw-tnm 2022-06-23T09:59:19.813Z [CURL DBG] < x-amz-id-2: l4qurc28-v01aw-tnm 2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Origin: * 2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Credentials: true 2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS 2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Allow-Headers: Content-Type,Content-MD5,Authorization,X-Amz-User-Agent,X-Amz-Date,ETag,X-Amz-Content-Sha256 2022-06-23T09:59:19.813Z [CURL DBG] < Access-Control-Expose-Headers: ETag,X-Amz-Version-Id 2022-06-23T09:59:19.813Z [CURL DBG] < Content-Type: application/xml 2022-06-23T09:59:19.813Z [CURL DBG] < Content-Length: 215 2022-06-23T09:59:19.813Z [CURL DBG] < Date: Thu, 23 Jun 2022 09:59:19 GMT 2022-06-23T09:59:19.813Z [CURL DBG] < Connection: keep-alive 2022-06-23T09:59:19.813Z [CURL DBG] < Keep-Alive: timeout=5 2022-06-23T09:59:19.813Z [CURL DBG] < ``` ### Details about issue - while executing **ls** command from s3fs-fuse client on mount path we error in debug mode also at the same time we are getting below error in s3 endpoint ``` Jun-23 10:00:12.541 [Endpoint/11] [ERROR] core.endpoint.s3.s3_rest:: S3 ERROR <?xml version="1.0" encoding="UTF-8"?><Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message> <Resource>/my-bucket/level-6/</Resource><RequestId>l4qusgrz-djbgdn-15mm</RequestId> </Error> HEAD /my-bucket/level-6/ {"host":"s3.openshift-storage:80","user-agent":"s3fs/1.91 (commit hash unknown; OpenSSL)","accept":"*/*","authorization":"AWS4-HMAC-SHA256 Credential=cwhl3ut6KMorHppPBtIH/20220623/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2ab2fad4ef3ec22c3fb78fa26151e61a37dbee887ac156f905c6f065fe34c95e","x-amz-content-sha256":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","x-amz-date":"20220623T100012Z"} [RpcError: No such object: obj_id undefined bucket SENSITIVE-d5bc0c9f50b30cee key level-8/] { rpc_code: 'NO_SUCH_OBJECT' } ```