[GH-ISSUE #843] Not able use option list_object_max_keys while mounting s3bucket onto ec2 #490

New issue

Closed

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

kerem commented

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

Owner

Originally created by @shashi1981 on GitHub (Oct 19, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/843

we were planning on increasing the list_object_max_keys to 5000 for a use case. but we are unable to use it.

error : fuse: unknown option `list_object_max_keys=5000'

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System V1.84(commit:c5af62b) 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, rpm -qi fuse, dpkg -s fuse)

Name : fuse
Version : 2.9.4

Kernel information (uname -r)

_command result: uname -r
4.14.72-68.55.amzn1.x86_64

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

command result: cat /etc/os-release
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"

s3fs command line used, if applicable

s3fs -o iam_role="role" -o dbglevel=info -o curldbg -o allow_other -o umask=0000 -o list_object_max_keys=5000 <s3-bucket-name>  /s3bucket

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

Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: [path=/][flags=100352]
Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: [path=/]
Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]:   [path=/]
Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]:       [tpath=/]
Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]:       URL is https://s3.amazonaws.com/<s3-bucket-name>?delimiter=/&max-keys=1000&prefix=
Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]:       URL changed is https://<s3-bucket-name>.s3.amazonaws.com?delimiter=/&max-keys=1000&prefix=
Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]:       [IAM role=role-name]
Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: * Connection 6 seems to be dead!

Details about issue

Errors out with Transport Endpoint error

Originally created by @shashi1981 on GitHub (Oct 19, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/843 we were planning on increasing the list_object_max_keys to 5000 for a use case. but we are unable to use it. error : fuse: unknown option `list_object_max_keys=5000' #### Version of s3fs being used (s3fs --version) Amazon Simple Storage Service File System V1.84(commit:c5af62b) 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, rpm -qi fuse, dpkg -s fuse) Name : fuse Version : 2.9.4 #### Kernel information (uname -r) _command result: uname -r 4.14.72-68.55.amzn1.x86_64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) _command result: cat /etc/os-release_ NAME="Amazon Linux AMI" VERSION="2018.03" ID="amzn" ID_LIKE="rhel fedora" VERSION_ID="2018.03" PRETTY_NAME="Amazon Linux AMI 2018.03" ANSI_COLOR="0;33" CPE_NAME="cpe:/o:amazon:linux:2018.03:ga" HOME_URL="http://aws.amazon.com/amazon-linux-ami/" #### s3fs command line used, if applicable ``` s3fs -o iam_role="role" -o dbglevel=info -o curldbg -o allow_other -o umask=0000 -o list_object_max_keys=5000 <s3-bucket-name> /s3bucket ``` #### 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_ ``` Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: [path=/][flags=100352] Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: [path=/] Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: [path=/] Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: [tpath=/] Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: URL is https://s3.amazonaws.com/<s3-bucket-name>?delimiter=/&max-keys=1000&prefix= Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: URL changed is https://<s3-bucket-name>.s3.amazonaws.com?delimiter=/&max-keys=1000&prefix= Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: [IAM role=role-name] Oct 15 18:38:01 ip-10-62-0-86 s3fs[19869]: * Connection 6 seems to be dead! ``` ### Details about issue Errors out with Transport Endpoint error