starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 05:16:00 +03:00

[GH-ISSUE #543] After mount the S3, return nothing #312

New issue

Closed

opened 2026-03-04 01:44:16 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:44:16 +03:00

Owner

Originally created by @TonyWuLihu on GitHub (Mar 10, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/543

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.

Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.80(commit:19f0d49) with OpenSSL
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Version of fuse being used (pkg-config --modversion fuse)
2.8.3
System information (uname -a)
x86_64 x86_64 x86_64 GNU/Linux
Distro (cat /etc/issue)
CentOS release 6.4 (Final)
Kernel \r on an \m
s3fs command line used (if applicable)

s3fs s3://mgtv-ott-data-archive /data/s3fs -o passwd_file=/etc/passwd-s3fs

/etc/fstab entry (if applicable):

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Nothing

Details about issue

After issued the command, there isn't any output, and the content in S3 hasn't mount to the mount point, ls /data/s3fs returns nothing

Originally created by @TonyWuLihu on GitHub (Mar 10, 2017). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/543 #### 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._ - Version of s3fs being used (s3fs --version) - Amazon Simple Storage Service File System V1.80(commit:19f0d49) with OpenSSL Copyright (C) 2010 Randy Rizun <rrizun@gmail.com> License GPL2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. - Version of fuse being used (pkg-config --modversion fuse) - 2.8.3 - System information (uname -a) - x86_64 x86_64 x86_64 GNU/Linux - Distro (cat /etc/issue) - CentOS release 6.4 (Final) Kernel \r on an \m - s3fs command line used (if applicable) ``` s3fs s3://mgtv-ott-data-archive /data/s3fs -o passwd_file=/etc/passwd-s3fs ``` - /etc/fstab entry (if applicable): ``` ``` - s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` Nothing ``` #### Details about issue After issued the command, there isn't any output, and the content in S3 hasn't mount to the mount point, ls /data/s3fs returns nothing

kerem

2026-03-04 01:44:16 +03:00

closed this issue
added the
duplicate
label

kerem commented

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

Author

Owner

@justinmchase commented on GitHub (Mar 25, 2017):

You can run it with the -f flag and then it will output something. If you also add the -d flag it will output a lot.

The thing is that when you run it like you did it is running as a daemon (aka in the background). Its output can't be streaming to you. The -f flag disables that.

@justinmchase commented on GitHub (Mar 25, 2017): You can run it with the `-f` flag and then it will output something. If you also add the `-d` flag it will output a lot. The thing is that when you run it like you did it is running as a daemon (aka in the background). Its output can't be streaming to you. The -f flag disables that.

kerem commented

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

Author

Owner

@TonyWuLihu commented on GitHub (Apr 18, 2017):

s3fs -f -d mgtv-ott-data-archive /data/s3fs/ -o passwd_file=/etc/s3fs/.passwd-s3fs -o url=http://s3.cn-north-1.amazonaws.com.cn -o endpoint=cn-north-1 -o curldbg -o f2
[CRT] s3fs.cpp:set_s3fs_log_level(254): change debug level from [CRT] to [INF]
[CRT] s3fs.cpp:set_s3fs_log_level(254): change debug level from [INF] to [DBG]
[INF] s3fs.cpp:set_mountpoint_attribute(4196): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)
[CRT] s3fs.cpp:s3fs_init(3375): init v1.80(commit:19f0d49) with OpenSSL
[WAN] curl.cpp:InitShareCurl(483): curl_share_setopt(SSL SESSION) returns 1(Unknown share option), but continue without shared ssl session data.
[INF] s3fs.cpp:s3fs_check_service(3753): check services.
[INF] curl.cpp:CheckBucket(2883): check a bucket.
[DBG] curl.cpp:GetHandler(272): Get handler from pool: 31
[INF] curl.cpp:prepare_url(4199): URL is http://s3.cn-north-1.amazonaws.com.cn/mgtv-ott-data-archive/
[INF] curl.cpp:prepare_url(4231): URL changed is http://mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn/
[INF] curl.cpp:insertV4Headers(2260): computing signature [GET] [/] [] []
[INF] curl.cpp:url_to_host(100): url is http://s3.cn-north-1.amazonaws.com.cn
[DBG] curl.cpp:RequestPerform(1916): connecting to URL http://mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn/

About to connect() to mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn port 80 (#0)
Trying 54.222.21.14... * connected
Connected to mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn (54.222.21.14) port 80 (#0)

GET / HTTP/1.1
User-Agent: s3fs/1.80 (commit hash 19f0d49; OpenSSL)
Accept: /
Authorization: AWS4-HMAC-SHA256 Credential=AKIAO22EENO5CK26FFGA/20170418/cn-north-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=49f3bfee821fc8749ef6170789ef221ede6b5aa0bfbe82a1114d0b9b7835bd74
host: mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20170418T070924Z

< HTTP/1.1 200 OK
< x-amz-id-2: BIDk68q0AIxSWJe71PD037Awg/SGnNEYoT8U7idEvVPIof40Wq0stoWnebzhP2sDQKt+0Dc3PaE=
< x-amz-request-id: B398EC69003FEC12
< Date: Tue, 18 Apr 2017 07:09:25 GMT
< x-amz-bucket-region: cn-north-1
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Server: AmazonS3
<

Connection #0 to host mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn left intact
[INF] curl.cpp:RequestPerform(1933): HTTP response code 200
[DBG] curl.cpp:ReturnHandler(295): Return handler to pool: 31

@TonyWuLihu commented on GitHub (Apr 18, 2017): s3fs -f -d mgtv-ott-data-archive /data/s3fs/ -o passwd_file=/etc/s3fs/.passwd-s3fs -o url=http://s3.cn-north-1.amazonaws.com.cn -o endpoint=cn-north-1 -o curldbg -o f2 [CRT] s3fs.cpp:set_s3fs_log_level(254): change debug level from [CRT] to [INF] [CRT] s3fs.cpp:set_s3fs_log_level(254): change debug level from [INF] to [DBG] [INF] s3fs.cpp:set_mountpoint_attribute(4196): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777) [CRT] s3fs.cpp:s3fs_init(3375): init v1.80(commit:19f0d49) with OpenSSL [WAN] curl.cpp:InitShareCurl(483): curl_share_setopt(SSL SESSION) returns 1(Unknown share option), but continue without shared ssl session data. [INF] s3fs.cpp:s3fs_check_service(3753): check services. [INF] curl.cpp:CheckBucket(2883): check a bucket. [DBG] curl.cpp:GetHandler(272): Get handler from pool: 31 [INF] curl.cpp:prepare_url(4199): URL is http://s3.cn-north-1.amazonaws.com.cn/mgtv-ott-data-archive/ [INF] curl.cpp:prepare_url(4231): URL changed is http://mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn/ [INF] curl.cpp:insertV4Headers(2260): computing signature [GET] [/] [] [] [INF] curl.cpp:url_to_host(100): url is http://s3.cn-north-1.amazonaws.com.cn [DBG] curl.cpp:RequestPerform(1916): connecting to URL http://mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn/ * About to connect() to mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn port 80 (#0) * Trying 54.222.21.14... * connected * Connected to mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn (54.222.21.14) port 80 (#0) > GET / HTTP/1.1 User-Agent: s3fs/1.80 (commit hash 19f0d49; OpenSSL) Accept: */* Authorization: AWS4-HMAC-SHA256 Credential=AKIAO22EENO5CK26FFGA/20170418/cn-north-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=49f3bfee821fc8749ef6170789ef221ede6b5aa0bfbe82a1114d0b9b7835bd74 host: mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 x-amz-date: 20170418T070924Z < HTTP/1.1 200 OK < x-amz-id-2: BIDk68q0AIxSWJe71PD037Awg/SGnNEYoT8U7idEvVPIof40Wq0stoWnebzhP2sDQKt+0Dc3PaE= < x-amz-request-id: B398EC69003FEC12 < Date: Tue, 18 Apr 2017 07:09:25 GMT < x-amz-bucket-region: cn-north-1 < Content-Type: application/xml < Transfer-Encoding: chunked < Server: AmazonS3 < * Connection #0 to host mgtv-ott-data-archive.s3.cn-north-1.amazonaws.com.cn left intact [INF] curl.cpp:RequestPerform(1933): HTTP response code 200 [DBG] curl.cpp:ReturnHandler(295): Return handler to pool: 31

kerem commented

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

Author

Owner

@TonyWuLihu commented on GitHub (Apr 18, 2017):

I tried other options, but this time, it hangs up forever while I tried to mount the bucket like above

@TonyWuLihu commented on GitHub (Apr 18, 2017): I tried other options, but this time, it hangs up forever while I tried to mount the bucket like above

kerem commented

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

Author

Owner

@ggtakec commented on GitHub (May 5, 2017):

@TonyWuLihu
This case is like(same) #475.
Maybe you specify bucket name with "s://" prefix, you do not need to use "s://" prefix.
And s3fs put no error message at exiting, then I fixed new codes to master branch.
Please try to use new codes and you do not specify prefix.

I'm closing this issue, but if you have more problem, please reopen this issue.
Rergards,

@ggtakec commented on GitHub (May 5, 2017): @TonyWuLihu This case is like(same) #475. Maybe you specify bucket name with "s://" prefix, you do not need to use "s://" prefix. And s3fs put no error message at exiting, then I fixed new codes to master branch. Please try to use new codes and you do not specify prefix. I'm closing this issue, but if you have more problem, please reopen this issue. Rergards,