[GH-ISSUE #2226] "File too large" when trying to add or edit a file or folder #1133

New issue

Closed

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

kerem commented

2026-03-04 01:51:38 +03:00

Owner

Originally created by @zilti on GitHub (Jul 20, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2226

Additional Information

Version of s3fs being used (`s3fs --version`)

V1.92 (commit:unknown) with OpenSSL

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

2.9.9

Kernel information (`uname -r`)

13.2-RELEASE

Operating System

FreeBSD

How to run s3fs, if applicable

[] command line
[X] /etc/fstab

nextcloud       /usr/local/www/nextcloud/data   fuse    rw,_netdev,allow_other,mountprog=/usr/local/bin/s3fs,late,passwd_file=/usr/local/etc/passwd-s3fs,url=https://s3.pub1.infomaniak.cloud,use_path_request_style,use_cache=/tmp/s3fs,enable_noobj_cache,no_check_certificate,use_xattr,complement_stat,enable_content_md5,use_wtf8,bucket_size=500TiB       0       0

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

Jul 20 13:48:40 lyrion s3fs[1356]: s3fs_logger.cpp:LowSetLogLevel(239): change debug level from [CRT] to [INF]
Jul 20 13:48:40 lyrion s3fs[1356]: curl.cpp:InitMimeType(403): Could not find mime.types files, you have to create file(/etc/mime.types) or specify mime option for existing mime.types file.
Jul 20 13:48:40 lyrion s3fs[1356]: s3fs.cpp:main(5527): Missing MIME types prevents setting Content-Type on uploaded objects.
Jul 20 13:48:40 lyrion s3fs[1359]: s3fs_cred.cpp:VersionS3fsCredential(60): Check why built-in function was called, the external credential library must have VersionS3fsCredential function.
Jul 20 13:48:40 lyrion s3fs[1359]: *   Trying XXX.XXX.XX.XX:443...
Jul 20 13:48:40 lyrion s3fs[1359]: * Connected to s3.pub1.infomaniak.cloud (XXX.XXX.XX.XX) port 443 (#0)
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (OUT), TLS handshake, Client hello (1):
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Server hello (2):
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Certificate (11):
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, CERT verify (15):
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Finished (20):
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (OUT), TLS handshake, Finished (20):
Jul 20 13:48:40 lyrion s3fs[1359]: * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
Jul 20 13:48:40 lyrion s3fs[1359]: * Server certificate:
Jul 20 13:48:40 lyrion s3fs[1359]: *  subject: CN=api.pub1.infomaniak.cloud
Jul 20 13:48:40 lyrion s3fs[1359]: *  start date: Apr 10 00:00:00 2023 GMT
Jul 20 13:48:40 lyrion s3fs[1359]: *  expire date: Apr 23 23:59:59 2024 GMT
Jul 20 13:48:40 lyrion s3fs[1359]: *  subjectAltName: host "s3.pub1.infomaniak.cloud" matched cert's "s3.pub1.infomaniak.cloud"
Jul 20 13:48:40 lyrion s3fs[1359]: *  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
Jul 20 13:48:40 lyrion s3fs[1359]: *  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
Jul 20 13:48:40 lyrion s3fs[1359]: > GET /nextcloud/ HTTP/1.1
Jul 20 13:48:40 lyrion s3fs[1359]: > Host: s3.pub1.infomaniak.cloud
Jul 20 13:48:40 lyrion s3fs[1359]: > User-Agent: s3fs/1.92 (commit hash unknown; OpenSSL)
Jul 20 13:48:40 lyrion s3fs[1359]: > Accept: */*
Jul 20 13:48:40 lyrion s3fs[1359]: > Authorization: AWS4-HMAC-SHA256 Credential=c848973c6ba441bcb9bd582cb7df9169/20230720/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=c82774db8107f04fe415f7665cacf6457c3d4ba396ac3fdcccf8c4c800a79c6f
Jul 20 13:48:40 lyrion s3fs[1359]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Jul 20 13:48:40 lyrion s3fs[1359]: > x-amz-date: 20230720T134840Z
Jul 20 13:48:40 lyrion s3fs[1359]: >  
Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
Jul 20 13:48:40 lyrion syslogd: last message repeated 1 times
Jul 20 13:48:40 lyrion s3fs[1359]: * old SSL session ID is stale, removing
Jul 20 13:48:40 lyrion s3fs[1359]: < HTTP/1.1 200 OK 
Jul 20 13:48:40 lyrion s3fs[1359]: < content-type: application/xml 
Jul 20 13:48:40 lyrion s3fs[1359]: < content-length: 328038
Jul 20 13:48:40 lyrion s3fs[1359]: < x-amz-id-2: tx5a48afc32641429bb3551-0064b93b38
Jul 20 13:48:40 lyrion s3fs[1359]: < x-amz-request-id: tx5a48afc32641429bb3551-0064b93b38
Jul 20 13:48:40 lyrion s3fs[1359]: < x-trans-id: tx5a48afc32641429bb3551-0064b93b38
Jul 20 13:48:40 lyrion s3fs[1359]: < x-openstack-request-id: tx5a48afc32641429bb3551-0064b93b38
Jul 20 13:48:40 lyrion s3fs[1359]: < date: Thu, 20 Jul 2023 13:48:40 GMT
Jul 20 13:48:40 lyrion s3fs[1359]: < strict-transport-security: max-age=63072000
Jul 20 13:48:40 lyrion s3fs[1359]: < 
Jul 20 13:48:40 lyrion s3fs[1359]: * Connection #0 to host s3.pub1.infomaniak.cloud left intact

Details about issue

I can successfully mount the Swift bucket using s3fs and access and delete files. If I want to create a file or directory, however, or change a file, I get a "File too large" error.

Originally created by @zilti on GitHub (Jul 20, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2226 ### Additional Information #### Version of s3fs being used (`s3fs --version`) V1.92 (commit:unknown) with OpenSSL #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) 2.9.9 #### Kernel information (`uname -r`) 13.2-RELEASE #### Operating System FreeBSD #### How to run s3fs, if applicable  [] command line [X] /etc/fstab  ``` nextcloud /usr/local/www/nextcloud/data fuse rw,_netdev,allow_other,mountprog=/usr/local/bin/s3fs,late,passwd_file=/usr/local/etc/passwd-s3fs,url=https://s3.pub1.infomaniak.cloud,use_path_request_style,use_cache=/tmp/s3fs,enable_noobj_cache,no_check_certificate,use_xattr,complement_stat,enable_content_md5,use_wtf8,bucket_size=500TiB 0 0 ``` #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`) ``` Jul 20 13:48:40 lyrion s3fs[1356]: s3fs_logger.cpp:LowSetLogLevel(239): change debug level from [CRT] to [INF] Jul 20 13:48:40 lyrion s3fs[1356]: curl.cpp:InitMimeType(403): Could not find mime.types files, you have to create file(/etc/mime.types) or specify mime option for existing mime.types file. Jul 20 13:48:40 lyrion s3fs[1356]: s3fs.cpp:main(5527): Missing MIME types prevents setting Content-Type on uploaded objects. Jul 20 13:48:40 lyrion s3fs[1359]: s3fs_cred.cpp:VersionS3fsCredential(60): Check why built-in function was called, the external credential library must have VersionS3fsCredential function. Jul 20 13:48:40 lyrion s3fs[1359]: * Trying XXX.XXX.XX.XX:443... Jul 20 13:48:40 lyrion s3fs[1359]: * Connected to s3.pub1.infomaniak.cloud (XXX.XXX.XX.XX) port 443 (#0) Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (OUT), TLS handshake, Client hello (1): Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Server hello (2): Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Certificate (11): Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, CERT verify (15): Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Finished (20): Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (OUT), TLS handshake, Finished (20): Jul 20 13:48:40 lyrion s3fs[1359]: * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 Jul 20 13:48:40 lyrion s3fs[1359]: * Server certificate: Jul 20 13:48:40 lyrion s3fs[1359]: * subject: CN=api.pub1.infomaniak.cloud Jul 20 13:48:40 lyrion s3fs[1359]: * start date: Apr 10 00:00:00 2023 GMT Jul 20 13:48:40 lyrion s3fs[1359]: * expire date: Apr 23 23:59:59 2024 GMT Jul 20 13:48:40 lyrion s3fs[1359]: * subjectAltName: host "s3.pub1.infomaniak.cloud" matched cert's "s3.pub1.infomaniak.cloud" Jul 20 13:48:40 lyrion s3fs[1359]: * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA Jul 20 13:48:40 lyrion s3fs[1359]: * SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway. Jul 20 13:48:40 lyrion s3fs[1359]: > GET /nextcloud/ HTTP/1.1 Jul 20 13:48:40 lyrion s3fs[1359]: > Host: s3.pub1.infomaniak.cloud Jul 20 13:48:40 lyrion s3fs[1359]: > User-Agent: s3fs/1.92 (commit hash unknown; OpenSSL) Jul 20 13:48:40 lyrion s3fs[1359]: > Accept: */* Jul 20 13:48:40 lyrion s3fs[1359]: > Authorization: AWS4-HMAC-SHA256 Credential=c848973c6ba441bcb9bd582cb7df9169/20230720/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=c82774db8107f04fe415f7665cacf6457c3d4ba396ac3fdcccf8c4c800a79c6f Jul 20 13:48:40 lyrion s3fs[1359]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Jul 20 13:48:40 lyrion s3fs[1359]: > x-amz-date: 20230720T134840Z Jul 20 13:48:40 lyrion s3fs[1359]: > Jul 20 13:48:40 lyrion s3fs[1359]: * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): Jul 20 13:48:40 lyrion syslogd: last message repeated 1 times Jul 20 13:48:40 lyrion s3fs[1359]: * old SSL session ID is stale, removing Jul 20 13:48:40 lyrion s3fs[1359]: < HTTP/1.1 200 OK Jul 20 13:48:40 lyrion s3fs[1359]: < content-type: application/xml Jul 20 13:48:40 lyrion s3fs[1359]: < content-length: 328038 Jul 20 13:48:40 lyrion s3fs[1359]: < x-amz-id-2: tx5a48afc32641429bb3551-0064b93b38 Jul 20 13:48:40 lyrion s3fs[1359]: < x-amz-request-id: tx5a48afc32641429bb3551-0064b93b38 Jul 20 13:48:40 lyrion s3fs[1359]: < x-trans-id: tx5a48afc32641429bb3551-0064b93b38 Jul 20 13:48:40 lyrion s3fs[1359]: < x-openstack-request-id: tx5a48afc32641429bb3551-0064b93b38 Jul 20 13:48:40 lyrion s3fs[1359]: < date: Thu, 20 Jul 2023 13:48:40 GMT Jul 20 13:48:40 lyrion s3fs[1359]: < strict-transport-security: max-age=63072000 Jul 20 13:48:40 lyrion s3fs[1359]: < Jul 20 13:48:40 lyrion s3fs[1359]: * Connection #0 to host s3.pub1.infomaniak.cloud left intact ``` ### Details about issue I can successfully mount the Swift bucket using s3fs and access and delete files. If I want to create a file or directory, however, or change a file, I get a "File too large" error.