Issue creating/uploading a file to s3 mount

[netpez]

We are experimenting with utilizing an s3 mount to store files uploaded through a Lucee application. I have enabled allow overwrite and allow delete, however, the developer is reporting that when attempting to upload a file to the s3 mount, that upon first attempt (which fails), an empty file is created, however, the file is uploaded successfully upon the second attempt.

I could use some advise on this... has anyone run into this situation, or have any input on possible configuration I am missing?

[passaro]

Hi @netpez, have you had a look at our troubleshooting guide? In particular, there are some limitations when writing to files with Mountpoint. For example, only sequential writes are allowed, see the semantics documentation for details.

If you still need help, we suggest enabling logging in Mountpoint (see logging documentation). Once you reproduce the issue, we can help analyzing the logs if needed (please also include the command used to launch Mountpoint).

[netpez]

I have added the logging to the mount command, here is the command being used:

mount-s3 smhs-lucee-test /site --cache /cache --allow-overwrite --allow-delete --allow-other --log-directory /var/log/mount-s3/

Attached is the lucee application output.

lucee_errors.pdf

Here is the s3-mount log output after performing read/writes/deletes attemps from the lucee application

2025-03-11T01:01:25.165241Z WARN readdirplus{req=308 ino=2 fh=1 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/") has an invalid name and will be unavailable
2025-03-11T01:01:25.234187Z WARN readdirplus{req=324 ino=2 fh=2 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/") has an invalid name and will be unavailable
2025-03-11T01:01:25.248749Z WARN readdirplus{req=330 ino=2 fh=3 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/") has an invalid name and will be unavailable
2025-03-11T01:01:25.261884Z WARN readdirplus{req=344 ino=2 fh=4 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/") has an invalid name and will be unavailable
2025-03-11T01:01:25.275046Z WARN readdirplus{req=352 ino=2 fh=5 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/") has an invalid name and will be unavailable
2025-03-11T01:01:25.323682Z WARN readdirplus{req=378 ino=2 fh=6 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/") has an invalid name and will be unavailable
2025-03-11T01:15:44.093342Z WARN readdirplus{req=1822 ino=11 fh=7 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/lucee_tests/") has an invalid name and will be unavailable
2025-03-11T01:15:44.137956Z WARN readdirplus{req=1838 ino=11 fh=8 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/lucee_tests/") has an invalid name and will be unavailable
2025-03-11T01:15:44.695857Z WARN open{req=1964 ino=21 pid=103 name="test.txt"}: mountpoint_s3::fuse: open failed with errno 1: inode error: inode 21 (full key "web/acws/test.txt") is already being written
2025-03-11T01:15:46.651978Z WARN readdirplus{req=1974 ino=2 fh=14 offset=0}: mountpoint_s3::superblock::readdir: file '' (full key "web/") has an invalid name and will be unavailable
2025-03-11T01:15:47.151976Z WARN open{req=2034 ino=23 pid=103 name="test.txt"}: mountpoint_s3::fuse: open failed with errno 1: inode error: inode 23 (full key "err/acws/test.txt") is already being written
2025-03-11T01:15:47.431919Z WARN open{req=2078 ino=25 pid=103 name="test.txt"}: mountpoint_s3::fuse: open failed with errno 1: inode error: inode 25 (full key "data/acws/test.txt") is already being written
2025-03-11T01:15:47.729221Z WARN getxattr{req=2114 ino=26 name="security.selinux"}: mountpoint_s3::fuse: getxattr failed: operation not supported by Mountpoint
2025-03-11T01:15:48.317076Z WARN unlink{req=2116 parent=24 name="test.txt"}: mountpoint_s3::fuse: unlink failed with errno 2: inode error: file "test.txt" does not exist in parent inode 24 (full key "data/acws/")
2025-03-11T01:15:48.423683Z WARN unlink{req=2140 parent=22 name="test.txt"}: mountpoint_s3::fuse: unlink failed with errno 2: inode error: file "test.txt" does not exist in parent inode 22 (full key "err/acws/")
2025-03-11T01:16:33.653626Z WARN open{req=2388 ino=48 pid=102 name="test.txt"}: mountpoint_s3::fuse: open failed with errno 1: inode error: inode 48 (full key "web/acws/test.txt") is already being written
2025-03-11T01:16:33.898658Z WARN open{req=2440 ino=49 pid=102 name="test2.txt"}: mountpoint_s3::fuse: open failed with errno 1: inode error: inode 49 (full key "err/acws/test2.txt") is already being written
2025-03-11T01:16:34.624158Z WARN unlink{req=2522 parent=22 name="test2.txt"}: mountpoint_s3::fuse: unlink failed with errno 2: inode error: file "test2.txt" does not exist in parent inode 22 (full key "err/acws/")