Tell us more about this new feature.
We have a situation where mount-s3 is fronting S3 buckets with some objects that aren't named very well. The size of this bucket makes it impractical for us to fix all of the S3 object names. We end up with large /var/log/messages files with the following WARN messages:
Feb 28 23:59:10 host-01 mount-s3[1491]: [WARN] ThreadId(16) readdirplus{req=562924082 ino=695189655 fh=67483048 offset=0}: mountpoint_s3_fs::superblock::readdir: file '' (full key "foo/bar/rearr/") has an invalid name and will be unavailable
We are running:
mount-s3 1.20.0
On Rocky 9 linux.
The logging options don't seem to include a mode to log only ERRORs. That would be nice to still log errors, but ignore warnings.
Logging options:
-l, --log-directory <DIRECTORY>
Write log files to a directory [default: logs written to syslog]
--log-metrics
Enable logging of summarized performance metrics
-d, --debug
Enable debug logging for Mountpoint
--debug-crt
Enable debug logging for AWS Common Runtime
--no-log
Disable all logging. You will still see stdout messages.
Tell us more about this new feature.
We have a situation where mount-s3 is fronting S3 buckets with some objects that aren't named very well. The size of this bucket makes it impractical for us to fix all of the S3 object names. We end up with large /var/log/messages files with the following WARN messages:
We are running:
mount-s3 1.20.0
On Rocky 9 linux.
The logging options don't seem to include a mode to log only ERRORs. That would be nice to still log errors, but ignore warnings.