[GH-ISSUE #1166] S3FS API calls #611

New issue

Closed

opened 2026-03-04 01:47:12 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:47:12 +03:00

Owner

Originally created by @Lilitapudane on GitHub (Oct 10, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1166

Version of s3fs being used (s3fs --version)

1.85

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

2.9.2

Kernel information (uname -r)

_command result: 3.10.0-957.12.2.el7.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"

Details about issue

Hi,
We are interested in S3FS use, so now we are testing, if it's fits our needs.
I have following question, how I can see S3FS API calls which are going to aws, for example when I'm trying to copy something from S3 bucket: aws s3 cp s3://bucket/file-name

I tried with tcpdump src , but it didn't showed me anything.

Originally created by @Lilitapudane on GitHub (Oct 10, 2019). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1166 #### Version of s3fs being used (s3fs --version) 1.85 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) 2.9.2 #### Kernel information (uname -r) _command result: 3.10.0-957.12.2.el7.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" ### Details about issue Hi, We are interested in S3FS use, so now we are testing, if it's fits our needs. I have following question, how I can see S3FS API calls which are going to aws, for example when I'm trying to copy something from S3 bucket: aws s3 cp s3://bucket/file-name I tried with tcpdump src <IP>, but it didn't showed me anything.

kerem closed this issue

2026-03-04 01:47:13 +03:00

kerem commented

2026-03-04 01:47:13 +03:00

Author

Owner

@AgrawalAmey commented on GitHub (Oct 10, 2019):

@Lilitapudane check curldbg option. -d -d -f -o curldbg should print detailed debug logs.

@AgrawalAmey commented on GitHub (Oct 10, 2019): @Lilitapudane check `curldbg` option. `-d -d -f -o curldbg` should print detailed debug logs.

kerem commented

2026-03-04 01:47:13 +03:00

Author

Owner

@gaul commented on GitHub (Oct 10, 2019):

curldbg is the easiest but if you want to use tcpdump you probably want to connect via http instead of https.

@gaul commented on GitHub (Oct 10, 2019): `curldbg` is the easiest but if you want to use tcpdump you probably want to connect via http instead of https.

kerem commented

2026-03-04 01:47:14 +03:00

Author

Owner

@mrPsycho commented on GitHub (Oct 11, 2019):

perfect, thanks!

@mrPsycho commented on GitHub (Oct 11, 2019): perfect, thanks!

kerem referenced this issue

2026-03-04 02:01:07 +03:00

[PR #611] [MERGED] Fixed clock_gettime build failure on macOS 10.12 Sierra - #600 #1573